Re: Final, no really, Final draft: Conventions and Guidelines for Perl Source Code

2001-09-08 Thread Dave Mitchell
Robert Spier <[EMAIL PROTECTED]> wrote > >>How about something a little more explicit than XXX, like TODO or FIXME? > > Some syntax-highlighting editors highlight "XXX". Let's use that feature. > > > Which ones? emacs doesn't seem to do it by default. > > > > And how can you get more explici

Re: Final, no really, Final draft: Conventions and Guidelines for Perl Source Code

2001-09-07 Thread Robert Spier
>>How about something a little more explicit than XXX, like TODO or FIXME? > Some syntax-highlighting editors highlight "XXX". Let's use that feature. Which ones? emacs doesn't seem to do it by default. > And how can you get more explicit than XXX, anyway? Funny, but I still think TODO or

Re: Final, no really, Final draft: Conventions and Guidelines for Perl Source Code

2001-08-30 Thread Simon Cozens
On Thu, Aug 30, 2001 at 01:40:15PM -0400, Sam Tregar wrote: > What I've seen so far resembles a software CPU, which be analogy should be > able to do anything from run Quake III to compile Java. Does that mean > it's well-suited to compiling Perl? The interpreter is highly unsuited to *compiling

Re: Final, no really, Final draft: Conventions and Guidelines for Perl Source Code

2001-08-30 Thread Simon Cozens
On Thu, Aug 30, 2001 at 01:25:37PM -0400, Sam Tregar wrote: > On Wed, 29 Aug 2001, Simon Cozens wrote: > > It's almost time to start coding, people, almost. > Not to be an ass, but is it? Yes. > It seems like we're still a long way from having a language spec. That's not entirely relevant any

Re: Final, no really, Final draft: Conventions and Guidelines for Perl Source Code

2001-08-30 Thread Simon Cozens
On Thu, Aug 23, 2001 at 08:11:26PM -0400, Robert Spier wrote: > How about something a little more explicit than XXX, like TODO or FIXME? Some syntax-highlighting editors highlight "XXX". Let's use that feature. And how can you get more explicit than XXX, anyway? > > In function definitions, the

Re: Final, no really, Final draft: Conventions and Guidelines for Perl Source Code

2001-08-25 Thread Dan Sugalski
At 08:11 PM 8/23/2001 -0400, Robert Spier wrote: >Just some brief comments... $0.02 or some such. :) > > The top-level structure of the Perl source tarball should be as > > follows: > > > > /README, etca few top-level documents > > /doc/ Assorted miscellaneous documentation

Re: Final, no really, Final draft: Conventions and Guidelines for Perl Source Code

2001-08-24 Thread Robert Spier
Just some brief comments... $0.02 or some such. :) -R Quoting Dave Mitchell <[EMAIL PROTECTED]>: > =item * > > "K&R" style for indenting control constructs: ie the closing C<}> > should > line up with the opening C etc. You should provide a short example here - K&R has lots of nasties, you

Final, no really, Final draft: Conventions and Guidelines for Perl Source Code

2001-08-23 Thread Dave Mitchell
Okay, this really, really *really* the final draft. can I have a PDD number, please Dan? The only change since last is the stuff about if/else layout. Dave M. =head1 TITLE Conventions and Guidelines for Perl Source Code =head1 VERSION =head2 CURRENT Maintainer: Dave Mitchell <[EMAIL P