In writing up the RFC on removing/fixing $[line noise here] variables,
I've decided to leave out the following suggestion:
On Tue, Aug 01, 2000 at 06:47:41PM -0700, Nathan Wiger wrote:
> Alan Burlison wrote:
> >
> > Steve Simmons wrote:
> >
> > > I'd prefer that we break these vars out into a s
Larry Wall wrote:
> Some of these concepts are not going to be global concepts in Perl 6.
> The per-filehandle variables will be attached to filehandle objects.
THANK YOU!! (Breathes a sigh of relief.)
I still remember the fateful day when I discovered $", which made my
CGI script outpu
Steve Simmons writes:
: On Tue, Aug 01, 2000 at 04:47:47PM -0400, Dan Sugalski wrote:
:
: > Put together an RFC for it. (Soon!) This is a language topic, but it will
: > impact internals a touch, and I'd like to get as many of the "impact
: > internals" things spec'd out as soon as possible . .
On Wed, Aug 02, 2000 at 01:48:36PM -0600, Tom Christiansen wrote:
> >Isn't this covered by locales?
> Unicode and locales are immiscible.
In Perl 5. This is *by no means* a general statement.
ICU is, for instance, a Unicode locale library.
--
Gosh that takes me back... or is it forward? That's
On Wed, Aug 02, 2000 at 03:34:56PM -0400, John Porter wrote:
> Brust, Corwin wrote:
> > I want perl's error (and warning) messages to be specific to each program I
> > write.
>
> Isn't this covered by locales?
Completely different beast. I don't claim to fully understand locales,
but that's n
>Isn't this covered by locales?
Unicode and locales are immiscible.
--tom
Brust, Corwin wrote:
>
> messages.rfc - An RFC to discussing the wisdom of allowing run time error
> and warning messages to be modified at run time
> ...
> I want perl's error (and warning) messages to be specific to each program I
> write.
Isn't this covered by locales?
--
John Porter
Steve Simmons <[EMAIL PROTECTED]> writes:
> For deprecation, we should have a %PERL_DEPRECATED{mod}{thing} hash as
> well. `mod' is `CORE', `FORMATS', etc, as above. A value of 0 means the
> function is actually gone, 1 means it's disappearing next major release,
> 2 mean next minor, etc. The p
At 06:47 PM 8/1/00 -0700, Nathan Wiger wrote:
>Now *that's* an advantage I like! Being able to turn on certain warnings
>just for certain packages (rather than just a global all-or-nothing $^W)
>would be really cool.
Like, like... Lexical Warnings! Now *that* would be a keen idea! :)
Alan Burlison wrote:
>
> Steve Simmons wrote:
>
> > I'd prefer that we break these vars out into a set of hashes with
> > appropriate names:
> >
> > $PERL_CORE{warnings} vs $^W
> > $PERL_CORE{version} vs $^V
> > $PERL_FORMATS{name} vs $^
> > $P
ure there's a B way to implement this. I hope,
however, that I have shown such a thing can be done.
=head1 REFERENCES
=cut
-Original Message-
From: Dan Sugalski [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 01, 2000 3:48 PM
To: Brust, Corwin; 'Steve Simmons'; Perl6 Lang
At 04:58 PM 8/1/00 -0400, Steve Simmons wrote:
>On Tue, Aug 01, 2000 at 04:47:47PM -0400, Dan Sugalski wrote:
>
> > Put together an RFC for it. (Soon!) This is a language topic, but it will
> > impact internals a touch, and I'd like to get as many of the "impact
> > internals" things spec'd out as
ay, August 01, 2000 3:48 PM
To: Brust, Corwin; 'Steve Simmons'; Perl6 Language Changes
Subject: RE: Removing/fixing $[line noise here] variables
Put together an RFC for it. (Soon!) This is a language topic, but it will
impact internals a touch, and I'd like to get as many of the &
Steve Simmons wrote:
> I'd prefer that we break these vars out into a set of hashes with
> appropriate names:
>
> $PERL_CORE{warnings} vs $^W
> $PERL_CORE{version} vs $^V
> $PERL_FORMATS{name} vs $^
> $PERL_FORMATS{lines_left} vs $-
H
On Tue, Aug 01, 2000 at 04:47:47PM -0400, Dan Sugalski wrote:
> Put together an RFC for it. (Soon!) This is a language topic, but it will
> impact internals a touch, and I'd like to get as many of the "impact
> internals" things spec'd out as soon as possible . . .
Uh, OK - but how about we wa
Nathan Torkington wrote:
> Perhaps reserve the PERL or Perl namespace?
>
> $PERL::CORE{warnings}
> $PERL::FORMATS{name}
We remember that packages with lc names are already reserved by convention;
and this is one place to exploit that. [why "Config", anyway?]
$perl::core{warnings}
At 03:53 PM 8/1/00 -0500, Brust, Corwin wrote:
>Could this then also give the programer control over the content of
>error/warning messages produced by Perl at runtime?
That's feasable. It'd be a performance hit, but I can't picture this really
being a performance-critical area... :)
Put togeth
Could this then also give the programer control over the content of
error/warning messages produced by Perl at runtime?
Am I way off track here?
-Corwin
-Original Message-
From: Steve Simmons [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 01, 2000 3:37 PM
To: Perl6 Language Changes
S
Steve Simmons writes:
> I'd prefer that we break these vars out into a set of hashes with
> appropriate names:
>
> $PERL_CORE{warnings}vs $^W
> $PERL_CORE{version} vs $^V
> $PERL_FORMATS{name} vs $^
> $PERL_FORMATS{lines_left} vs $-
P
19 matches
Mail list logo
