Re: Source Code Control and Naming ThingiePoo was Re: Starting Perl

2003-11-13 Thread Chuk Goodin
On Thu, Nov 13, 2003 at 11:33:14AM -0800, drieux wrote: > So let us step back and look at the 'root cause problem' > > so I want to just 'fix it on the fly' > > and yes, foo.pl as an editable text file will allow you > simply open it with a text editor and WHACK a fix in. Unlike > RealCode[

Re: Starting Perl

2003-11-13 Thread Chuk Goodin
> >What kind of naming structure would you suggest for people who just > >want > >to use extensions for organizational purposes? > > when you say for 'organizational purposes' do you > mean in terms of tracking the 'source code' in a > source code control system? Or do you mean tracking > named a

Re: Starting Perl

2003-11-13 Thread Chuk Goodin
On Wed, Nov 12, 2003 at 07:55:24PM -0800, Randal L. Schwartz wrote: > Rob> Perl programs conventionally go in *.pl files. > > No. Only on broken architectures that demand it (read: "windows"). > On Unix, Perl programs have no extension, any more than "cat" has an > extension. Why should the user