Hi -

> -----Original Message-----
> From: Gazi, Nasser (London) [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 26, 2003 2:42 AM
> To: beginners
> Subject: Name of current perl script on Win32
>
>
> Hi,
>
> How can I find the name the perl script on Win32?
>
> I know that the usual way is to use $0
>
> However, this gives me a problem on Win32 with filenames bigger than 8
> characters, where $0 returns filename filename like "FIILEMAME~" which is
> useless to me.
>
> Help! And thanks.
>
> NG
> (Can't wait to get back to Unix)
>

On my system:

System Information report written at: 02/26/2003 10:40:11 AM
[System Summary]

Item    Value
OS Name Microsoft Windows 2000 Professional
Version 5.0.2195 Service Pack 3 Build 2195
OS Manufacturer Microsoft Corporation
System Name     ROCKY
System Manufacturer     VIA
System Model    7VTXE+
System Type     X86-based PC
Processor       x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1539 Mhz
BIOS Version    Version 1.00
Windows Directory       C:\WINNT
System Directory        C:\WINNT\System32
Boot Device     \Device\Harddisk0\Partition1
Locale  United States
User Name       ROCKY\beau
Total Physical Memory   392,688 KB
Available Physical Memory       15,468 KB
Total Virtual Memory    1,795,500 KB
Available Virtual Memory        1,109,676 KB
Page File Space 1,402,812 KB
Page File       C:\pagefile.sys

the following script:

 Volume in drive C has no label.
 Volume Serial Number is 405B-AE7C

 Directory of C:\_junk

02/26/2003  10:46a      <DIR>          .
02/26/2003  10:46a      <DIR>          ..
02/26/2003  10:31a                  13
this_perl_script_has_a_really_long_filename.pl
02/26/2003  10:46a                   0 x
               2 File(s)             13 bytes
               2 Dir(s)  23,224,504,320 bytes free

which is simply this:

print "$0\n";

returned:

this_perl_script_has_a_really_long_filename.pl

I do not get the "shortened" 8.3 name. ????

Aloha => Beau;



-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to