"Randal L. Schwartz" wrote:
> >>>>> "Rob" == Rob Dixon <[EMAIL PROTECTED]> writes:
>
> Rob> Perl programs conventionally go in *.pl files.
>
> No. Only on broken architectures that demand it (read: "windows").
Oh?
Greetings! E:\d_drive\ocf\discuss\prototype>perl mailparse
[Picture Tk-based interface coming up--working
perfectly--here]
Greetings! E:\d_drive\ocf\discuss\prototype>
Windows doesn't impose restrictions based on extensions. It simply offers
shortcuts based on them. The use of extensions provides a visible,
human-readable [excuse me while a change my fiename back--I don't like having to
call Perl explicitly...] indication of the type of data the file contains. When
we want the system to find the application to open a file, we use the convention
provided by the system.
The OP clearly specified that he was operating under Windows. Rob's advice was
right on the mark, since the ActiveState installations do not rely on the old .pl
extensions [Perl modules need no extension under Windows, since they are opened
programatically. I have associated the Edit command with Programmers File
Editor, though, for speedier right-click access]. Perl does use the extension
system for identifying modules under Windows. It looks specifically for files
with the .pm extension.
I just checked. Without an extension, the compiler couldn't find the module.
With the .pl extension, the compiler couldn't find the module. With the .pl
extension, the comiler couldn't find the module. The OS is not imposing this
limitation. The .pm extension has no magic for Windows, because neither the
installer program nor I have imbued it with any beyond the Edit association.
So what is the Perl issue here?
Joseph
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
