May I suggest the following extension to the 'use ' pragma, viz.
use module name written in unicode and case sensitive in filename as
constrained by local system
For justification, see below.
asideThere were some hot replies to what I thought was a fairly
trivial question. A corollary
In a message dated Mon, 7 Jan 2008, Richard Hainsworth writes:
May I suggest the following extension to the 'use ' pragma, viz.
use module name written in unicode and case sensitive in filename as
constrained by local system
Oh please, no.
The entire point of the wording currently in the
Trey Harris wrote:
In a message dated Mon, 7 Jan 2008, Richard Hainsworth writes:
May I suggest the following extension to the 'use ' pragma, viz.
use module name written in unicode and case sensitive in filename
as constrained by local system
Oh please, no.
The entire point of the wording
In a message dated Mon, 7 Jan 2008, Richard Hainsworth writes:
Yet, does my proposal *force* this? Is it not possible for the magical
resource locator to coexist with a mechanism to allow local control?
Yes--through CBEGIN blocks and munging, you can get whatever
complicated, platform- or
On Jan 7, 2008 1:34 PM, Richard Hainsworth [EMAIL PROTECTED] wrote:
snip
Definitely a good idea for the implementation / implementors to decide
how to get a resource magically.
But ...
I have run into situations where I wanted to have more control over
where specific resources were located,
Larry Wall skribis 2008-01-05 17:39 (-0800):
Already specced. (...)
It should probably mention Unicode there as well, but the principle is
already expressed in terms of case-sensitivity.
You're always a few steps ahead :)
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd
No, some people put .pl on the end of their scripts because they are
running on broken operating systems.
So, I imagine, for Perl6, I'll be making the same strong recommendation
that Perl6 scripts, just like Perl5 and Perl4 scripts before them, have
*no*
extension.
Randal L. Schwartz -
Richard Hainsworth skribis 2008-01-05 0:14 (+0300):
Perl scripts have had the extension *.pl
I usually only give throw-away scripts a .pl extension. Others I call
program and make executable, with no extension.
Trivial question, I suppose, but any reason not to use .p6?
It will look
On Sun, Jan 06, 2008 at 12:55:28AM +0100, Juerd Waalboer wrote:
: Personally I'm hoping for some extra abstraction in module filenames, to
: allow UTF-8 module names with ASCII filenames.
Already specced. From S02:
In the abstract, Perl is written in Unicode, and has consistent Unicode
Perl scripts have had the extension *.pl
To distinguish the scripts I started writing in perl6 from those in the
same directory written for perl5, I started naming perl6 scripts with
extension *.p6 .
Trivial question, I suppose, but any reason not to use p6? What will the
perl6 compiler
10 matches
Mail list logo
