David,
Thanks also for the tip. Now I am doubly noob...
> - UEdit column comment
> select your code to comment
> ALT+C (column edit)
> type # and spaces as you like it
>
> ++
> David "Sniper" Rigaudiere
>
>
> ___
> Perl-Win32-Users mailing list
> Perl-W
> To: "Bill Luebkert" <[EMAIL PROTECTED]>
> Cc:
> Sent: Monday, February 05, 2007 12:18 PM
> Subject: Re: Name of IF style
>
>
>>
>>> There are other ways to block out code in Perl. Personally, I use
>>> a vim macro and just comment out the bl
(/^xyz/) { $xyz = 1 }
06 # elsif (/^w12/) { $w12 = 1 }
07 # elsif (/^w34/) { $w34 = 1 }
08 else { $nothing = 1 }
09 }
10 }
--
Regards,
> -Original Message-
> From: [EMAIL PROTECTED]
> Subject: Re: Name of
>> There are other ways to block out code in Perl. Personally, I use
>> a vim macro and just comment out the block by marking the first line
>> (type ma [mark 'a' position]) and going to the last line and executing
>> the macro by hitting the key you have it bound to (I use #)
>>
> Lucky you. I am
A way I like to use to "comment out" code chunks is by turning them into
string literals. Type an aposotrophe at the beginning of the code block and
then another '; at the end of the block and everything in between is now a
string literal called in void context. Just have to make sure there are n
Message -
From: "Foo JH" <[EMAIL PROTECTED]>
To: "Bill Luebkert" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, February 05, 2007 12:18 PM
Subject: Re: Name of IF style
>
>> There are other ways to block out code in Perl. Personally, I use
>> a
> There are other ways to block out code in Perl. Personally, I use
> a vim macro and just comment out the block by marking the first line
> (type ma [mark 'a' position]) and going to the last line and executing
> the macro by hitting the key you have it bound to (I use #)
>
Lucky you. I am us
Foo JH wrote:
> Taguchi san,
>
> I like the coding style below for one main reason: it's easy to comment
> out if needed.
No easier than any other method - other than it's compressed into
fewer lines - which also makes it less easily modified.
> IMHO good coding style should support the followi
Taguchi san,
I like the coding style below for one main reason: it's easy to comment
out if needed.
IMHO good coding style should support the following:
1. Easy to read. Puristic styles are a matter of opinion. I prefer to
maintain a hybrid concept between K&R, BSD, and none-of-the-above;
choo
Thanks for replies.
This type of style should be named for the first creator or first teller
to have firstly reffered to it, like K&R or Allman.
I made a silly script to find the first writer...
By my script the first person is M[irs]+. eagle.
C:\>FFIND_IF.pl > FFIF.log
C:/Perl/lib/CPAN.pm
C:/Pe
At 03:25 PM 2/3/2007 +0900, =?iso-2022-jp?B?GyRCRUQ4fRsoQiAbJEI5QBsoQg==?=
wrote:
>The code below is in the Camel book, and I like this style.
>Anyone knows the name of this style or there is no such a name?
>
>
>if(/^abc/) { $abc = 1 }
>elsif (/^def/) { $def = 1 }
>
田口 浩 wrote:
> Hello,
>
> The code below is in the Camel book, and I like this style.
> Anyone knows the name of this style or there is no such a name?
>
>
> if(/^abc/) { $abc = 1 }
> elsif (/^def/) { $def = 1 }
> elsif (/^xyz/) { $xyz = 1 }
> else { $not
Hello,
The code below is in the Camel book, and I like this style.
Anyone knows the name of this style or there is no such a name?
if(/^abc/) { $abc = 1 }
elsif (/^def/) { $def = 1 }
elsif (/^xyz/) { $xyz = 1 }
else { $nothing = 1 }
-
13 matches
Mail list logo
