Prev: PERL to mean what 'perldoc perl' says is wrong? (was: Re: perlshould be improved and perl6)
Next: Can "perldoc" take input from a pipe?
From: nolo contendere on 16 Apr 2008 16:34
On Apr 16, 1:04 pm, Marek <ms...(a)podiuminternational.org> wrote:
> Sorry to bother this group again! Now my script is nearly finished.
> Only one little problem is left: I am imaging the perl "rename" like
> the shell "mv". Is there a difference? My rename is not working as
> intended:
>
> could not rename your pix from:
>         /Users/marekstepanek/Documents/webpages/www.munich-taxis.de/
> pix/fotos/thumbnails/tn_munich28.jpg
> to
>         /Users/marekstepanek/Documents/webpages/www.munich-taxis.de/
> pix_out/fotos/thumbnails/tn_munich28.jpg
>

check out File::Copy::move()
From: Dr.Ruud on 20 Apr 2008 04:50
Ted Zlatanov schreef:
> Lawrence Statton wrote:

>> You young'ns don't remember the great whitespace shortage of '03
>> ... all the new python people were using all the whitespace that
>> could be produced -- a lot of programmers had to go mining in old
>> COBOL and FORTRAN projects of their college days just to get enough
>> whitespace to keep our variables separated.
>
> Perl, fortunately, was not affected by this shortage by design :)

Per 6 is too modern for that:
"Whitespace is in general required between any keyword and any opening
bracket that is not introducing a subscript or function arguments. Any
keyword followed directly by parentheses will be taken as a function
call instead."

sub if { exit 1 }

--
Affijn, Ruud

"Gewoon is een tijger."

First  |  Prev  | 
Pages: 1 2 3
Prev: PERL to mean what 'perldoc perl' says is wrong? (was: Re: perlshould be improved and perl6)
Next: Can "perldoc" take input from a pipe?