tried to syntax-check this JAPH of Abigail's and MacPerl not only choked on
it but started writing itty-bitty lines of nonsense graphical data to the
center of the screen.
sub f{sprintf$_[0],$_[1],$_[2]}print
f('%c%s',74,f('%c%s',117,f('%c%s',115,f('%c%s',116,f('%c%s',32,f('%c%s',97,f
('%c%s',0x6
On Sun, 04 Mar 2001 05:32:25 -0500, Scott R. Godin wrote:
>tried to syntax-check this JAPH of Abigail's and MacPerl not only choked on
>it but started writing itty-bitty lines of nonsense graphical data to the
>center of the screen.
>
>sub f{sprintf$_[0],$_[1],$_[2]}print
>f('%c%s',74,f('%c%s',11
Abstract:
1) MacPerl open() call does not demand exclusive access for writing.
2) MPW tool version induces system crash.
3) stat() $nlink doesn't work.
A recent thread "grab a web wage" has caused me to go back into some scripting I did
to access daily prices for mutual funds that don't publish
At 14:01 -0700 2001.03.04, Doug McNutt wrote:
>Abstract:
>1) MacPerl open() call does not demand exclusive access for writing.
+< does not mean you are asking for exclusive access. I'm not sure why you
think it does.
>2) MPW tool version induces system crash.
I've heard of problems with callin
One for the Perl gurus on the list- not a major problem but more of a
philosophical debate, while doing some date related work I noticed that
sprintf() & printf() didn't behave as I expected them to, the following
snippet:
#!perl-w
printf("%2d",((localtime(time))[5])),"\n";
yields '101' not '01'
[EMAIL PROTECTED] wrote:
> ...
> printf("%2d",((localtime(time))[5]-100)),"\n";
> ... why don't printf() and sprintf() pad numbers with zeros
> and strings with spaces?
> Robin
Your question resembles a bit to the question about the special
degree of curvedness of some bananas.
Neverthele
At 6:33 +0900 3/5/01, [EMAIL PROTECTED] wrote:
>?One for the Perl gurus on the list- not a major problem but more of a
>philosophical debate, while doing some date related work I noticed that
>sprintf() & printf() didn't behave as I expected them to, the following
>snippet:
>
>#!perl-w
>
>printf("
on 03/04/2001 06:12 AM, Bart Lateur at [EMAIL PROTECTED] wrote:
> On Sun, 04 Mar 2001 05:32:25 -0500, Scott R. Godin wrote:
>
>> tried to syntax-check this JAPH of Abigail's and MacPerl not only choked on
>> it but started writing itty-bitty lines of nonsense graphical data to the
>> center of t
I'm something of an old-timer, having learned (s)printf as a C coder
(pre-ANSI). The idiom that I internalized when I wanted to get leading zeros
instead of leading spaces was:
printf( "%2.2d", someInt );
And this still works, in perl the same as it does in C (except for having to
p
On 5:59 PM 3/4/01 John W Baxter <[EMAIL PROTECTED]> wrote:
> At 6:33 +0900 3/5/01, [EMAIL PROTECTED] wrote:
> >?One for the Perl gurus on the list- not a major problem but more of
> >a philosophical debate, while doing some date related work I noticed
> >that sprintf() & printf() didn't behave as
Jim Correia <[EMAIL PROTECTED]> wrote:
>This from the same person who just posted, in separate thread:
>> follow the 3 golden rules of posting-
>> 1] Read the PODs
>> 2] Read the PODs
>> 3] Read the PODs
you were perfectly right Jim though I wasn't asking about time() or
localtime() :-), had I do
11 matches
Mail list logo
