This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Perl should not abort when a required file yields a false value
=head1 VERSION
Maintainer: Dominus <[EMAIL PROTECTED]>
Date: 21 Sep 2000
Last Modified: 23 Sep 2000
Mailing List: [EMAIL PROTECTED]
Piers Cawley wrote:
>
> By declaring a variable as being one of many types you throw away any
> possible compile time optimizations that may be possible (unless you
> add the restriction that said types have a common interface...)
>
> Note that a possible syntax for doing what you want could be:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
crypt() default salt
=head1 VERSION
Maintainer: Mark Dominus <[EMAIL PROTECTED]>
Date: 11 Sep 2000
Last Modified: 23 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 208
Version: 4
Status: Fro
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Add 'tristate' pragma to allow undef to take on NULL semantics
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 23 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 275
Versio
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Add null() keyword and fundamental data type
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 19 Sep 2000
Last Modified: 23 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 263
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Fix C<$pkg::$var> precedence issues with parsing of C<::>
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 14 Aug 2000
Last Modified: 23 Sep 2000
Mailing List: [EMAIL PROTECTED]
N
I have an RFC already in the works that addresses these with additions
to C. Hopefully out RSN.
-Nate
=item perl6storm #0003
Make parens "optionally mandatory" on function calls.
use strict 'functions';
=item perl6storm #0035
Make A->B place A in string context, like => does.
That way no
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0101
Just like the "use english" pragma (the modern not-yet-written
version of "use English" module), make something for legible
fileops.
is_readable(file) is really -r(file)
note that these are hard to write now due to
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0043
Write something that spits out module dependencies. Like makedep.
A tool that sources but doesn't run? a program/module then spits
out %INC might suffice. Can we autobundle with CPAN tricks?
Sounds good. Here's some stuff we had discussed on it:
http://www.mail-archive.com/perl6-language@perl.org/msg03484.html
http://www.mail-archive.com/perl6-language@perl.org/msg03487.html
http://www.mail-archive.com/perl6-language@perl.org/msg03488.html
http://www.mail-archive.com/perl6-language@p
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0026
Make CGI programming easier. Make as first class as
@ARGV and %ENV for CLI progging.
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0025
Make -T the default when operating in a CGI env. That is, taintmode.
Will this kill us? Close to it. Tough. Insecurity through idiocy
is a problem. Make them *add* a switch to make it insecure, like
-U, if that's wha
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0004
Need perl to spit out pod/non-pod, like cc -E. Pod is too hard to parse.
This would make catpod trivially implemented as a compiler filter.
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0022
make marshalling easy. core module? would this allow for easy
persistence of data structures other than dbm files?
general persistence is hard, right? can this be an attribute?
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #
This:
($a,$b) = ;
should not drain whole ahndle on known LHS count, to rescue
my($x) = ;
Russ Allbery wrote:
use 'strict' is probably the difference between our code... I tend not to use
it, because I wrote a bunch of code that didn't, initially, before I heard of
it (maybe before it existed? I started with Perl 4.something), and haven't
gotten it all converted so that it can be us
Nathan Wiger wrote:
> Jeremy Howard wrote:
> >
> > Good question. I haven't tackled this in RFC 83, because it is a more
> > general question about attribute syntax. We don't really have a good
> > attribute syntax RFC yet, although Nate threw up some ideas a couple of
days
> > ago. Is someone int
Glenn Linderman <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:
>> Perhaps I don't use those warnings in the same way that you do. I
>> *very* rarely have undefined value warnings in my programs, and when I
>> do they're usually not actually bugs, just things that require a
>> different way of
> =head1 TITLE
>
> Perl should not abort when a required file yields a false value
Damian already covered this in RFC 55: http://dev.perl.org/rfc/55.pod
-Nate
Just so we don't rehash issues that are already covered in other RFC's,
since many are:
> =item perl6storm #0015
>
> merge tie and overloading. python's ease of doing this
> makes this embarrassing.
RFC 200: Objects: Revamp tie to support extensibility (Massive tie
changes)
> =item perl6storm
Jeremy Howard wrote:
>
> Good question. I haven't tackled this in RFC 83, because it is a more
> general question about attribute syntax. We don't really have a good
> attribute syntax RFC yet, although Nate threw up some ideas a couple of days
> ago. Is someone interested in whipping up an RFC t
On Sat, 23 Sep 2000 04:20:37 -0400 (EDT), Philip Newton wrote:
>On Thu, 21 Sep 2000, Tom Christiansen wrote:
>
>> =item perl6storm #0035
>>
>> Make A->B place A in string context, like => does.
>> That way no A()->B naughtiness.
>
>While still allowing explicit A()->B?
Of course. You can still
> On Thu, 21 Sep 2000, Tom Christiansen wrote:
>
> > =item perl6storm #0050
> >
> > Radical notion: consider removing precedence.
> > Wrong precedence makes people miserable.
>
> (Some people already suggest that Perl only has two precedence rules: (1)
> multiplication and division come before add
Philip Newton <[EMAIL PROTECTED]> writes:
> On Thu, 21 Sep 2000, Tom Christiansen wrote:
>> =item perl6storm #0011
>> perl w/o args with stdin and out ttys should be perl -de 0.
>> saves novices from typing "perl" and getting confuddled.
> I think it should print out a banner message, too.
> A
On Thu, 21 Sep 2000, Tom Christiansen wrote:
> =item perl6storm #0073
>
> kill bareword strings entirely.
Including in places such as use? Well, I suppose we can get used to
use 'strict';
. Any other "famous" incidences of barewords? (Maybe
'Foo::Blurf'->meth().)
Cheers,
Philip
--
Phili
On Thu, 21 Sep 2000, Tom Christiansen wrote:
> =item perl6storm #0060
>
> formats and html doesn't mix nicely (not wysiwig). Neither do any
> hidden chars, like ESC-blah. Can we do more for generating simple
> clean transparent xml?
Talking of ESC-blah, I've sometimes wanted to have a way to
On Thu, 21 Sep 2000, Tom Christiansen wrote:
> =item perl6storm #0050
>
> Radical notion: consider removing precedence.
> Wrong precedence makes people miserable.
(Some people already suggest that Perl only has two precedence rules: (1)
multiplication and division come before addition and subtr
On Thu, 21 Sep 2000, Tom Christiansen wrote:
> =item perl6storm #0035
>
> Make A->B place A in string context, like => does.
> That way no A()->B naughtiness.
While still allowing explicit A()->B?
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
On Thu, 21 Sep 2000, Tom Christiansen wrote:
> =item perl6storm #0011
>
> perl w/o args with stdin and out ttys should be perl -de 0.
> saves novices from typing "perl" and getting confuddled.
I think it should print out a banner message, too.
A couple of times I was wondering whether perl was
On Thu, 21 Sep 2000, Tom Christiansen wrote:
> =item perl6storm #0010
>
> Allow a way to kill *all* defaults at compile time. Or warn about them.
>
> no defaults;
> use defaults 'none';
> use warnings 'defaults';
>
> this is for anal python folks.
What are defaults, in this conte
30 matches
Mail list logo
