My First Perl Project II

Hello everyone. I realized after reading a few replies to "My First Perl Project" I posted may have offended a few people who do run perl on Windows, and I apologise, I didn't mean any offense. I just didn't know how to make it work because I was a beginner, and all of that was new to me. I also do not have any problem with Windows, even though I prefer how Linux is much more efficient for me, personally. As a matter of fact, since my school uses Windows on their computers, and most of my software is formatted for Windows, I do have my Linux double booted to Windows 98SE :). I think it makes up for the few things that I do not have installed in my version of Linux :). Anyway, I just wanted to say sorry for anything that might have been taken wrong :). I would like to build this meditation on the old saying that two heads are better than one, and say that two OS's are better that one.

Comment on My First Perl Project II

Replies are listed 'Best First'.
Re: My First Perl Project II by demerphq (Chancellor) on Feb 17, 2004 at 23:22 UTC
saying that two heads are better than one, and say that two OS's are better that one. I think that one thing is that OS wars arent really appreciated in the perl community. Sure there is a heavy *nix leaning, and sure there is a heavy dislike of MS strong arm tactics, but the reality is that perl runs (or should run) everywhere. It should be as maximally portable as possible. (Hence the name of the dev group is called perl5porters) Theres a general agreement that while we may have our biases we probably shouldnt bring them up in the perl context. I imagine you fell foul of that. But i think you are probably on the right track. Understanding what makes Windows popular, understanding the needs and requirements of the common stupid noobie luser is essential to writing good software (if it interacts with users anyway). Using two OS'es with different designs and philosophies can only improve your skills and broaden your horizons. And the fact is that as a computer programmer its quite likely that at some point someone will tell you to code on Win32. Knowing how to do so will be an asset. --- demerphq _{First they ignore you, then they laugh at you, then they fight you, then you win. -- Gandhi}	[reply] [d/l]
Re: Re: My First Perl Project II by CloneArmyCommander (Friar) on Feb 18, 2004 at 16:26 UTC
Thank you :). I have realized my error, and I am glad to say that my fellow perl monks have corrected me, and I realize what I did wrong, and I have changed :).	[reply]
Re: My First Perl Project II by diotalevi (Canon) on Feb 17, 2004 at 19:15 UTC
For any who wonder, the original post is at My First Perl Project.	[reply]
Re: My First Perl Project II by rinceWind (Monsignor) on Feb 18, 2004 at 17:31 UTC
I would like to build this meditation on the old saying that two heads are better than one, and say that two OS's are better that one. That's the spirit. One of the great attractions of Perl is that it is available on a multitude of platforms. This means that it is possible (and usually desirable) to write portable code. However, the argument that because perl itself is portable, programs written in it are portable, is a fallacy. Consider hardcoded references to "/dev/tty" or "C:\Program Files". It's also not just a compatibility issue between Unix and Windows. I learned Perl on VMS, which has a vastly different syntax for filenames. Also note that the Apple Mac (prior to OS X) uses colons to delimit file paths. Filename syntax is only one portability issue. For the full monte, see perldoc perlport, supplied with the distribution. I have also given a talk on portability recently, with slides. -- I'm Not Just Another Perl Hacker	[reply]