On Mon, 31 Jul 2000, Nathan Wiger wrote:
> Instead, it would be really cool if Perl6 let you do this:
>
>#! perl -T
>local($^T) = 0;
>$ENV{PATH} = read_config_file();
>local($^T) = 1;
I would prefer something like:
#! perl -T
$ENV{PATH} = untaint( read_config_file() );
Dan Sugalski wrote:
>
> > existence of a $^T variable for controlling tainting in the same way
> > that $^W controls warnings.
>
> So put in an RFC. :)
Dan-
Ask and ye shall receive...in POD format ala Tim...
BTW, I've posted this to both lists because your reply was. However,
since $^T would
here is a set of minor syntax changes all involving adding the ability
to use my in more places. i think it (or parts of it) should be added to
skud's list. i don't know whether this has to be discussed and/or made
into an rfpc.
1. have grep, map and for modifier support a my $var like for does
(Cc'd to perl6-internals, which is where most of this is going)
On Mon, 31 Jul 2000, Nathan Wiger wrote:
> I can't find the full original thread, but somewhere it was suggested
> that $^O be removed because it's the same as $OSNAME. Again, I'm against
> this, I use it all the time.
$Config{osnam
On Mon, 31 Jul 2000, Bryan C. Warnock wrote:
> I don't think we're advocating its (their) complete demise, just the
> transition out of the core. (Which would, of course, still require a
> change to the scripts to 'use Format;'. Hmmm, perhaps all of
> formatting that is left in the core would b
> "DC" == Damian Conway <[EMAIL PROTECTED]> writes:
DC> Only if you simultaneously remove Perl 5!
DC> My (limited) understanding of the aims of Perl 6 were to start again with a
DC> clean slate and fix the things that are broken, or that could be designed
DC> better with hindsight. Backward
I can't find the full original thread, but somewhere it was suggested
that $^O be removed because it's the same as $OSNAME. Again, I'm against
this, I use it all the time.
However, this got me thinking. Here is an idea I'd like to see: The
existence of a $^T variable for controlling tainting in t
On Mon, 31 Jul 2000, Matthew Persico wrote:
> Which leads me to the question:
>
> Where do we discuss where to install modules? The prime question being
> how do we keep modules installed for multiple versions of Perl? I
> haven't yet seen that discussion, but it is one I want to participate
> in
> "MP" == Matthew Persico <[EMAIL PROTECTED]> writes:
MP> The original format stuff HAS to be kept. Don't document it so as not to
MP> encourage its use. Play up Text::Autoformat::form if you wish, but there
MP> will be way too much breakage/too little updateage if hundreds of old
MP> web log
> TJ> The month and day indices should stay zero since they are array
> TJ> indices. The manual will reflect this.
>
> [rspier@localhost rspier]$ perl -wle 'print +(localtime)[3] '
> 31
>
> To what index do you refer?
>
> month days are currently 1 based.
>
> _consistency_ would be nice, C b
> Chuckle, chuckle. Gee I guess we need more voices like yours to remind
> us what the goal is. I guess it is all too easy for any one person to
> locate their one or two small pieces of Perl turf they don't want
> touched. Problem is, when you add up all those little pieces, you end u
Great. Let's see if/how this list works.
Edwin Wiles wrote:
> I've already thrown a few notes together for a perl5 module, but nothing
> I'm ready to share just yet. I need to dig through CPAN to make sure
> I'm not reinventing something.
When you are ready to share, I'll be glad to peruse.
Damian Conway wrote:
>
>> Of all the items up for change in Perl6, these two bother me the most.
>> Format less so than localtime, but I still worry about breakage.
>>
>> The original format stuff HAS to be kept. Don't document it so as not to
>> encourage its use. Play up Tex
TJ> The month and day indices should stay zero since they are array
TJ> indices. The manual will reflect this.
[rspier@localhost rspier]$ perl -wle 'print +(localtime)[3] '
31
To what index do you refer?
month days are currently 1 based.
_consistency_ would be nice, C be dammed.
I propose "c
Simon Cozens wrote:
>
> On Mon, Jul 31, 2000 at 11:14:34PM -0400, Matthew Persico wrote:
> > The original format stuff HAS to be kept. Don't document it so as not to
> > encourage its use.
>
> Deliberately leaving things undocumented? I'm sorry, you must have us
> confused with another language.
Damian Conway writes:
> My (limited) understanding of the aims of Perl 6 were to start again with a
> clean slate and fix the things that are broken, or that could be designed
> better with hindsight. Backwards compatibily was to be fed to the lions.
Larry's the one who will decide what goes int
> > Language
> > -> Unixcentrism
> > -> 1.PROBLEM: localtime's behaviour is non-intuitive for non-Unix people
> >
> > (I've always wondered is why it is 'non-intuitive'? If 0 == January is
> > a problem. What do they do to translate day-of-week? Is it Monday
> > based or Sunday based. Don
On Mon, Jul 31, 2000 at 11:14:34PM -0400, Matthew Persico wrote:
> The original format stuff HAS to be kept. Don't document it so as not to
> encourage its use.
Deliberately leaving things undocumented? I'm sorry, you must have us
confused with another language.
--
Doubt is a pain too lonely to
On Mon, 31 Jul 2000, Matthew Persico wrote:
> The original format stuff HAS to be kept. Don't document it so as not to
> encourage its use. Play up Text::Autoformat::form if you wish, but there
> will be way too much breakage/too little updateage if hundreds of old
> web log scripts have to be ri
I was asked to repost this here. I didn't realize perl6-language was up
yet. My bad, sorry. :-)
-Nate
Original Message
Subject: Re: perl 6 requirements
Date: Mon, 31 Jul 2000 19:57:42 -0700
From: Nathan Wiger <[EMAIL PROTECTED]>
To: Chaim Frenkel <[EMAIL PROTECTED]>
CC: [EMAIL
> Of all the items up for change in Perl6, these two bother me the most.
> Format less so than localtime, but I still worry about breakage.
>
> The original format stuff HAS to be kept. Don't document it so as not to
> encourage its use. Play up Text::Autoformat::form if you wish,
"Bryan C. Warnock" wrote:
>
> On Mon, 31 Jul 2000, [EMAIL PROTECTED] wrote:
>
> > How about a Format module that works pretty much exactly the same way
> > but isn't actually in the Perl core?
> >
>
> One of the original suggestions, I believe. In this case, because
> other stuff *does* exist,
On Mon, 31 Jul 2000, Edwin Wiles wrote:
> Theoretically, we do have a list now. I'm going to try using it. It's
> also a personal experiment, since I'm subscribed to 'all', but not to
> 'language'.
>
Works for me. Thanks, Ask!
> Not if I can help it! I've run into some fairly complex binar
On Mon, 31 Jul 2000, [EMAIL PROTECTED] wrote:
> How about a Format module that works pretty much exactly the same way
> but isn't actually in the Perl core?
>
One of the original suggestions, I believe. In this case, because
other stuff *does* exist, the Format.pm mod should just attempt (to t
> >Unless you replace it with something better. (Postscript or TeX or ...)
> >You'll have a hard time finding something that makes life so easy.
>
> How about a Format module that works pretty much exactly the same way
> but isn't actually in the Perl core?
I have a paper on that
Theoretically, we do have a list now. I'm going to try using it. It's
also a personal experiment, since I'm subscribed to 'all', but not to
'language'.
I've already thrown a few notes together for a perl5 module, but nothing
I'm ready to share just yet. I need to dig through CPAN to make sure
At 12:27 PM 8/1/00 +1000, [EMAIL PROTECTED] wrote:
>[ moved to perl6-language ]
>
>On Mon, Jul 31, 2000 at 02:40:20PM -0400, Chaim Frenkel wrote:
> >Unless you replace it with something better. (Postscript or TeX or ...)
> >You'll have a hard time finding something that makes life so easy.
>
>How
[ moved to perl6-language ]
On Mon, Jul 31, 2000 at 02:40:20PM -0400, Chaim Frenkel wrote:
>Language
> -> Obsolete Features
> -> 1. Formats are not commonly used
>
>I'm sorry where did this come from. I use formats regularly and quite
>usefully.
>
>I suspect that those folks that have
28 matches
Mail list logo
