Re: Final draft: Conventions and Guidelines for Perl Source Code

2001-08-15 Thread H . Merijn Brand
On Tue 14 Aug 2001 00:55, "Espen Harlinn" <[EMAIL PROTECTED]> wrote: > Pardon me for butting in at this late stage :-) > > Since the purpose of coding conventions and guidelines is to make code more > readable to the majority of developers, wouldn't it make sence to settle on > something that can

RE: Qouting and white-space etc..

2001-08-15 Thread Patel, Sharad
How Do I Unsubscribe ?? -Original Message- From: raptor [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 15, 2001 10:36 AM To: [EMAIL PROTECTED] Subject: Qouting and white-space etc.. hi, I was wondering if there was some way when using qouting to specify triming of white space or

Qouting and white-space etc..

2001-08-15 Thread raptor
hi, I was wondering if there was some way when using qouting to specify triming of white space or other type of charachters we may need ... say like TT or may be ...one example.. my $javascripCode = qq{ | |function blah() |if ( ) |}; | }; |<-inner

Re: Final draft: Conventions and Guidelines for Perl Source Code

2001-08-15 Thread Dave Mitchell
I think then we are all agreed that the format is /* comment */ if (...) { ... } /* comment */ else { ... } with mandatory {}s. For completeness, we should also include chained else-ifs; I think the following is reasonably uncontroversial: /* comment */ if (...) { ... } /* comment