On Tue, Aug 01, 2000 at 08:30:44AM -0700, Nathan Wiger wrote:
> So perhaps:
>
>#! perl -T
># [ ... ]
>{ local $^T = 0; $ENV{PATH} = $unsafe_data; }
># [ ... ]
>system "sh -c echo 'Hello, world!'"; # ?
I would rather have it as a pragm instead of a special var ie
use t
On Tue, Aug 01, 2000 at 11:59:22AM -0400, Chaim Frenkel wrote:
> Reduce (e.g. $x = reduce { sum } @list;
I mentioned this to Larry on the Friday after the conference
and his response was that he did think about it originally but
$sum = reduce + @list; # assuming I got the verbal
On Tue, Aug 01, 2000 at 07:41:59PM -0700, Randal L. Schwartz wrote:
> > "Chaim" == Chaim Frenkel <[EMAIL PROTECTED]> writes:
>
> Chaim> It's the overloading of the ',' operator.
>
> Just like the overloading of the @ARRAY_NAME operator or the
> getpwuid() operator. Perhaps you are back to m
On Tue, Aug 01, 2000 at 10:27:08PM +0300, Ariel Scolnicov wrote:
>multimap operation list-of-lists # uurgh.
This made me think of something else that came up in a discussion with Larry
after the conference.
The discussion started off with the ability to do
for ($a,$b) (@list) { ... }
On Wed, Aug 02, 2000 at 03:40:01PM +0200, Gisle Aas wrote:
> Graham Barr <[EMAIL PROTECTED]> writes:
>
> > On Tue, Aug 01, 2000 at 10:27:08PM +0300, Ariel Scolnicov wrote:
> > >multimap operation list-of-lists # uurgh.
> >
> > This made me th
On Wed, Aug 02, 2000 at 11:37:06AM -0400, Andy Dougherty wrote:
> On Wed, 2 Aug 2000, Chaim Frenkel wrote:
>
> > If it is decided (and I hope not) that localtime and its kin are verboten,
> > it should not exists _at all_ in Perl6 and any existance at all would be
> > only as a support module for
On Wed, Aug 02, 2000 at 09:26:42AM -0600, Tom Christiansen wrote:
> I believe that under the current proposal, any unqualified and
> hitherto undeclared variables would be implicitly declared to be
> lexicals in the current scope. This is to be contrasted with the
> status quo, under which such v
On Wed, Aug 02, 2000 at 09:41:06AM -0600, Tom Christiansen wrote:
> >> Well we should still have POSIX::localtime().
>
> >True, and hopefully in a more optimal form.
>
> Were you planning on updating the Standard? :-)
Sure, everything is up for grabs right :)
Actually I meant the way the POSI
On Wed, Aug 02, 2000 at 11:50:10AM -0400, Sam Tregar wrote:
> On 2 Aug 2000, Gisle Aas wrote:
>
> > =head1 PERL5 PORTABILITY
> >
> > Calls to time() could be transformed to int(time()) when converting
> > perl5 programs to perl6.
>
> Unless there's a:
>
>use HiRes::Time qw(time);
>
> in e
On Wed, Aug 02, 2000 at 08:45:05AM -0700, Randal L. Schwartz wrote:
> You need a list vs. array distinction. An operator can't return an
> array. It can only return a list. Unless you're inventing a
> different language. :)
You say "operator" and you are right. I think the issue is a sub
can
On Wed, Aug 02, 2000 at 06:15:48PM +0200, H.Merijn Brand wrote:
> If I could, I would VETO!
>
> This would break about 90% of my scripts. I use the same name for different
> type of variables to group them:
Why ? Remember there will (hopefully) be translation from perl5->perl6
so this could pote
On Wed, Aug 02, 2000 at 12:22:10PM -0400, John Porter wrote:
> I guess my question is, why do these need to be builtins?
They don't. But that does not mean they should not be considered.
> There is no limit to the funky algorithms one can come up with;
> not everyting should go in the core.
Tru
On Wed, Aug 02, 2000 at 12:07:31PM -0400, Dan Sugalski wrote:
> At 10:30 AM 8/2/00 -0400, Michael Mathews wrote:
> >Okay, I'm impressed. 108 messages in my box this morning from the list.
> >Shows spunk.
> >
> >But I'm concerned. Are you getting enough sleep?
>
> Of course not. :)
>
> Don't for
On Wed, Aug 02, 2000 at 09:42:09AM -0700, Randal L. Schwartz wrote:
> >>>>> "Graham" == Graham Barr <[EMAIL PROTECTED]> writes:
>
> Graham> You say "operator" and you are right. I think the issue is a sub
> Graham> can return either.
On Wed, Aug 02, 2000 at 10:43:37AM -0600, Tom Christiansen wrote:
> >sub mapf(&;\@\@\@\@\@\@\@\@\@) {
>
> Steal from lisp:
>
> map
> maap
> maaap
> mapp
> mappp
> maappp
dwim
:)
Graham.
On Wed, Aug 02, 2000 at 03:00:04PM -0400, Michael Mathews wrote:
> Ted Ashton wrote:
> > The qc()
> > proposal fits in well with the Perl "look-and-feel" and seems pretty
> > comfortable to me. If there are concerns about obfuscatory potential, a
> > use strict 'comments' could require that the q
On Wed, Aug 02, 2000 at 08:10:01PM +0100, Alan Burlison wrote:
> "Randal L. Schwartz" wrote:
>
> > Graham> sub def { my @a = (9,8,7); return @a; }
> >
> > That's not returning the array. That's returning a copy of the contents
> > of @a in a list context, and the number of elements of @a in a s
On Wed, Aug 02, 2000 at 07:36:09PM +0100, Tom Hughes wrote:
> In message <[EMAIL PROTECTED]>
> Gisle Aas <[EMAIL PROTECTED]> wrote:
>
> > The upcoming Python (v2.0) introduces a builtin called zip() that does
> > the same thing:
> >
> > for a,b,c in zip(aa,bb,cc):
> > ...
> >
>
On Thu, Aug 03, 2000 at 06:31:38AM +, Martyn J. Pearce wrote:
> And I feel that by being able to iterate over lists with map, grep,
> fold[rl]/reduce{,_r}, whatever, _without pre-flattening the list_, we
> could drastically increase the applicability of these constructs.
Having iterators aval
On Thu, Aug 03, 2000 at 06:27:13AM -0600, Tom Christiansen wrote:
> >It seems that this issue is definitely worth a quick RFC - something
> >like "proposal to return filehandles from open/opendir rather than supply
> >as arguments".
>
> What about the pids that come back from begotten processes,
On Thu, Aug 03, 2000 at 06:40:30AM -0600, Tom Christiansen wrote:
> >Modify open() and opendir() to return filehandle objects
>
> Here are some things that that will be a problem for:
I did not see any that would be a problem.
Graham.
On Thu, Aug 03, 2000 at 06:39:02AM -0700, Randal L. Schwartz wrote:
> Nope. Sometimes my brain prefers the EXPR if EXPR form because of
> the much smaller punctuation footprint. Removing the comma
> doesn't seem to serve anything but making Perl less powerful, and
> not confusing Chaim quite as
On Thu, Aug 03, 2000 at 07:11:00AM -0600, Tom Christiansen wrote:
> $fh = open("|-") || die "can't start pipeline: $!";
>
> if ($fh->pid) {
> print $fh "stuff\n";
> } else {
> $data = readline $fh;
> }
>
> I think I'd prefer that ->pid return 0 only to the child of
On Thu, Aug 03, 2000 at 08:13:09AM -0600, Tom Christiansen wrote:
> No, that's gross. A failed constructor should return undef. See my
> later message.
That has always been my view. But then people say "but why did it fail"
and having global variables does not scale well.
My comment comes mai
On Thu, Aug 03, 2000 at 10:02:44AM -0400, Tad McClellan wrote:
> It should be named wantlist()
I actually think there is a need for a more generic replacement, say
want() or context()
Graham.
On Thu, Aug 03, 2000 at 09:01:44AM -0600, Tom Christiansen wrote:
> >On Thu, Aug 03, 2000 at 08:13:09AM -0600, Tom Christiansen wrote:
> >> No, that's gross. A failed constructor should return undef. See my
> >> later message.
>
> >That has always been my view. But then people say "but why did
On Thu, Aug 03, 2000 at 09:41:07AM -0700, Peter Scott wrote:
> The last iteration of the Conway (nee Phoenix) proposal is at
> http://www.csse.monash.edu.au/~damian/Perl/want.proposal unless he's taken
> it elsewhere. It is (predictably) far more comprehensive than anything
> anyone else has c
On Tue, Aug 01, 2000 at 11:56:48AM -0400, Dan Sugalski wrote:
> What I was thinking of was something along the lines of a lexically scoped
> pragma--"use taint"/"no taint". (We could do this by sticking in an opcode
> to set/unset the tainting status, as well as the warning status, and so on)
>
On Fri, Aug 04, 2000 at 11:25:49AM +0200, Johan Vromans wrote:
> How does 'it went wrong' know _which_ of the subs went wrong? For
> example:
>
> try {
> open(file1);
> open(file2);
> open(file3);
> } catch {
> error("could not open one of the file(s)");
> }
>
> which is no
On Fri, Aug 04, 2000 at 05:09:13AM -0600, Tom Christiansen wrote:
> This is my argument against obsolescing the general-purpose socket() et al.
> syscalls in deference to the IO::Socket stuff:
Absolutly. A high level API is ok for those who want it. But you should
never take away the low-level s
On Fri, Aug 04, 2000 at 04:56:53AM -0600, Tom Christiansen wrote:
> > > What about '$me'? It ties in nicely with 'my' (although perhaps f
> > > wrong reasons), it's half as much typing as 'self' or 'this' and we get
> > > to annoy both sets of religious zealots at once. :-)=
>
> >You too
On Fri, Aug 04, 2000 at 02:59:06PM -, Perl6 RFC Librarian wrote:
> Howeverm it I possible to cause a C statement to "fall-through". If a
> C is executed within a C block, control is immediately
> transferred to the statement following the C block.
> For example:
>
> switch ($count) {
On Fri, Aug 04, 2000 at 02:57:45PM -, Perl6 RFC Librarian wrote:
> =item 'BOOLEAN'
>
> The subroutine was called in a boolean context:
>
> if ( func() ) {}
> $val = func() || 0;
> $val = func() or die;
This one is debateable. BOOLEAN could be seen as asking for a TR
On Wed, Aug 02, 2000 at 11:29:40AM -0400, Dan Sugalski wrote:
> I was figuring the taint/notaint pragma would control taint checking, while
> -T would control taint setting. Probably not the best way--might be worth
> unconditionally setting the taint status so a use/no taint would do the
> rig
On Sat, Aug 05, 2000 at 04:10:20AM +1000, Damian Conway wrote:
>> If a switch is considered like a loop then next would be the same
>> as 'break' in C, as would last and redo would repeat the switch.
>
> But a switch is not a loop.
True, but in perl any block is considered to be a loop t
On Tue, Aug 08, 2000 at 10:02:35AM +0100, Piers Cawley wrote:
> "Peter Bevan" <[EMAIL PROTECTED]> writes:
>
> > Just a thought, but I think it woul be a good idea to include the
> > 'java-esqe' practice of including packages via foo.barr.*
Hey, I'm famous :)
> However, I do like the idea of syn
On Sat, Aug 05, 2000 at 12:30:02AM -0600, Nathan Torkington wrote:
> Someone wrote:
> > > How about "Deprecate use of file globbing with angle brackets. Emit a
> > > warning when this behaviour is used."
>
> I want to RFC this, but I feel like starting a new language with
> deprecated behaviours
On Tue, Aug 08, 2000 at 08:53:30PM -0400, Dan Sugalski wrote:
> On Tue, 8 Aug 2000, Michael Mathews wrote:
>
> > Dan Sugalski said:
> > > > > * Do we even want to allow after-the-fact chomps, or do it
> > automagically
> > > >at read time?
> > > "Yes" is rather ambiguous.
> >
> > To clarify: "Ye
On Thu, Aug 10, 2000 at 02:56:59AM -0500, Jonathan Scott Duff wrote:
> Peter Scott writes:
> > try {
> > # fragile code
> > } catch Exception::IO with {
> > # handle IO exceptions
> > } catch Exception::Socket with {
> > # handle network exceptions
> > } oth
On Thu, Aug 10, 2000 at 09:34:43AM -0700, Peter Scott wrote:
> At 05:11 PM 8/10/00 +0100, Graham Barr wrote:
> >I was more thinking of
> >
> > eval {
> > # fragile code
> > }
> > else { # catc
On Thu, Aug 10, 2000 at 12:28:05PM -0400, Dan Sugalski wrote:
> No, it wouldn't, really. We could make "use fatal;" scoped, so that the
> quit op (or whatever it is) only jumps through all its hoops if the
> pragma's in effect. If its not, then quit(foo, bar, baz) does a bare return
> and that'
On Fri, Aug 11, 2000 at 06:22:46AM +1000, Damian Conway wrote:
> I don't *dislike* your proposal, except that it interposes another layer of
> indirection on a process that is already too slow.
>
>
>> =head2 $AUTOLOAD
>>
>> While w
the continue block, and marks the successful handling
>of the exception.
>
>
>
> >>>>> "GB" == Graham Barr <[EMAIL PROTECTED]> writes:
>
> GB> I was more thinking of
>
> GB> eval {
> GB> # fragile code
> GB> }
>
On Thu, Aug 10, 2000 at 10:43:02AM -0400, Bennett Todd wrote:
> If the only real problem that can be found with making module use
> package-local is in these few option-flag type variables, perhaps
> they could be handled differently. E.g. suppose normal package
> variables end up being local to t
On Thu, Aug 10, 2000 at 06:43:30PM -0400, Chaim Frenkel wrote:
> >>>>> "GB" == Graham Barr <[EMAIL PROTECTED]> writes:
>
> GB> On Thu, Aug 10, 2000 at 04:34:50PM -0400, Chaim Frenkel wrote:
> >> Nice.
> >>
> >> The continue
On Thu, Aug 10, 2000 at 07:30:53PM -0700, Peter Scott wrote:
> So I'm thinking:
>
> eval { ...
> } catch Exception::Foo {
>...
> } catch Exception::Bar, Exception::Baz {
>...
> } catch {
>... # everything else, but if this block is absent, uncaught exceptions
># head up the ca
On Thu, Aug 10, 2000 at 07:47:47PM -0600, Tony Olekshy wrote:
> With the approach proposed in RFC 88 (Structured Exception
> Handling Mechanism), you could write that as:
>
> try {
> } catch {
> switch ($_[0]->name) {
> case IO { ... }
> case Sock
On Thu, Aug 10, 2000 at 07:22:21PM -0400, Chaim Frenkel wrote:
> Okay, then for
>
> reduce &avg $identity, @list
>
> What should $identity be?
I would like to see what &avg would be, given that each time it
would be passed the previous result (or the first element) and
the next element.
On Fri, Aug 11, 2000 at 01:20:36PM +0200, Bart Lateur wrote:
> I think we don't really need reduce(). There are well working,
> relatively simple, and *far more transparent* alternatives, at least,
> for Perl. We do have OP= operators, after all. For example:
>
> $total = 0;
> map { $
On Thu, Aug 10, 2000 at 10:21:37PM -, Perl6 RFC Librarian wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Replace => (stringifying comma) with => (pair constructor)
>
> =head2 Pairs and arrays
>
> When a pair reference is assigned
On Fri, Aug 11, 2000 at 11:24:48AM +1000, Damian Conway wrote:
> This can be correctly handled. The named parameter's context specifier
> would be propagated to the right operand of the =>. So:
>
> sub demo ( $name, \%options ) {...}
>
> will accept:
>
> demo(options=>%myopts, name
On Fri, Aug 11, 2000 at 02:52:32AM -0700, Nathan Wiger wrote:
> Mike-
>
> Jeremy's got a great explanation of this, which I'll paraphrase, but the
> discussion went through lots of iterations. Think of the ^ as a carat or
> thumbtack, holding the place for later variables. Then, consider the
> pa
On Fri, Aug 11, 2000 at 01:47:12PM +0100, Piers Cawley wrote:
> > /^_/
> >
> > What is that matching ?
>
> We've done this. It's matching a string that begins with '_'. Which is
> why, if you want to disambiguate you do /^{_}/ just like you do with
> variables.
No that won't work either. Tha
On Fri, Aug 11, 2000 at 10:34:00AM -0400, John Porter wrote:
> I support the idea of renaming the block eval as die, and leaving eval
^^^
That would be interesting :)
> for string eval.
>
> But I'm against the idea of implicit rethrowing in any
On Fri, Aug 11, 2000 at 03:30:28PM -, Perl6 RFC Librarian wrote:
>
> =head1 ABSTRACT
>
> It is proposed that two new functions, C, and C, be added to
> Perl. C would return a list that interleaved
> its arguments. C would reverse this operation.
I know other languages call it zip, but perso
On Fri, Aug 11, 2000 at 03:36:21PM -, Perl6 RFC Librarian wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Builtin: partition
>
> =head1 VERSION
>
> Maintainer: Jeremy Howard <[EMAIL PROTECTED]>
> Date: 11 August 2000
> Versio
On Fri, Aug 11, 2000 at 04:22:33PM -, Perl6 RFC Librarian wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Replace localtime() and gmtime() with date() and gmtdate()
I think to be politically acceptable to all that should be utcdate
On Fri, Aug 11, 2000 at 10:51:45AM -0400, John Porter wrote:
> Damian Conway wrote:
> >
> > More and more I lean towards a scalar-only reduce.
>
> Yep!
Have you stollen my brain :)
Graham.
On Fri, Aug 11, 2000 at 10:26:25AM -0700, Peter Scott wrote:
> At 10:34 AM 8/11/00 -0400, John Porter wrote:
> >But I'm against the idea of implicit rethrowing in any case.
> >
> >Sure, other languages do it, but perl doesn't, and personally I think
> >it's a better paradigm.
>
> We may have to d
On Fri, Aug 11, 2000 at 06:25:07PM +0100, Andy Wardley wrote:
> > I know other languages call it zip, but personally I dislike that name
> > as zip() is commonly used with reference to compression. Although
> > I do not have a good alternative.
>
> fold() and unfold()?
People would confude that
On Thu, Aug 10, 2000 at 04:47:33PM -, Perl6 RFC Librarian wrote:
> cope with a method call, it should return undef. Perl would then walk
> the OO hierarchy and find the next AUTOLOAD to call, eventually failing
> with an error if no AUTOLOAD method is found which will accept the
> call.
Why n
On Wed, Aug 02, 2000 at 10:09:04PM -0600, Nathan Torkington wrote:
> In the future, if you want to submit an RFC mail it to
> [EMAIL PROTECTED] only. The automated process will send it to
> the correct list as well as to -announce. This will also prevent
> perl6-librarian being CC:ed on followup
On Tue, Aug 08, 2000 at 02:37:54PM -, Perl6 RFC Librarian wrote:
> =head3 blocks
>
> The C scoping pragma automatically scopes variables to the
> innermost B block. The key work here is anonymous. The main
> program itself is seen as the outermost block. So, this code:
>
>$x = 10;
>
On Tue, Aug 15, 2000 at 05:10:34PM -0400, Dan Sugalski wrote:
> Let's not move backwards and force people to work like machines. Instead,
> lets force machines to work like us.
I dred to think what kind of machine we would make :)
Graham.
On Wed, Aug 16, 2000 at 03:05:23PM -, Perl6 RFC Librarian wrote:
> =head1 ABSTRACT
>
> With a here doc print < the text of the here doc, is processed verbatum. This results in Here Docs
> that either stick out in the code, or result in unwanted leading whitespace.
> There are several FAQs t
On Wed, Aug 16, 2000 at 10:20:28AM -0500, Jonathan Scott Duff wrote:
> > m//gt would be defined to do the match, and return the count of matches, this
> > leaves all existing uses consistent and unaffected. /t is suggested for
> > "counT", as /c is already taken. Using /t without /g would be re
On Wed, Aug 16, 2000 at 10:49:16AM -0500, Jarkko Hietaniemi wrote:
> On Wed, Aug 16, 2000 at 04:41:33PM +0100, Graham Barr wrote:
> > On Wed, Aug 16, 2000 at 10:20:28AM -0500, Jonathan Scott Duff wrote:
> > > > m//gt would be defined to do the match, and return the c
On Wed, Aug 16, 2000 at 01:51:09PM -0600, Nathan Torkington wrote:
> Nathan Wiger writes:
> > Nonetheless, I think a better thing would be to figure out if it's
> > possible to "fix" this issue. I would *really* like lvalue subs ==
> > rvalue subs.
>
> I think conflating:
>foo(@vals)
> and
>
On Mon, Aug 28, 2000 at 04:10:01PM -0400, Eric Roode wrote:
> Peter Scott wrote:
> >Graham Barr once allowed as how he thought it would be neat if you could say
> >
> > for my($x, $y, $z) (@list) { ... }
>
> ObLanguageMinimalist:
>
> Um. Is this so frequen
On Thu, Aug 31, 2000 at 03:55:28PM +1100, Damian Conway wrote:
> And has anyone pointed out that C is just:
>
> sub list {@_}
Um no. I would expect it to be
sub list { @_[0..$#_] }
Graham.
On Fri, Sep 01, 2000 at 11:23:16AM -0700, Steve Fink wrote:
> I read your message and agree. Not that I liked the idea that much even
> before considering the ramifications. But do you agree that even
> seasoned perlers have trouble anticipating how a list/array is going to
> be converted to a sca
On Tue, Sep 05, 2000 at 11:16:48AM +1100, Damian Conway wrote:
>> By RFC 21, it looks like the call would be
>>
>>if ( want 'LIST' ) {
>> $num_to_return = want;
>> # do stuff
>>}
>
> or, more efficiently:
>
>if ( ($num_to_return) = want 'LIST'
On Wed, Sep 06, 2000 at 10:40:47AM +0200, Jonas Liljegren wrote:
> (I sent this to horos in the first RFC format, before the language
> list. I haven't got any response, so I send this agian now. I don't
> have time to read the list or maintain an RFC. I just wan't to give
> this suggestion.)
>
On Thu, Sep 07, 2000 at 07:44:31PM -0500, Jarkko Hietaniemi wrote:
> > Exactly the sort of chicanery grep/last is meant to avoid. So the question
> > becomes, how do we crowbar "last" in without altering the returned value in
> > C blocks. I'm for putting it after a comma. Which matches the synt
On Mon, Sep 11, 2000 at 04:41:29PM -0500, Jarkko Hietaniemi wrote:
> Allow me to repeat: instead of trying to shoehorn (or piledrive) new
> semantics onto existing keywords/syntax, let's create something new.
> The blocks of grep/map/... are special. They are not quite looping
> blocks, they are
On Thu, Sep 14, 2000 at 08:10:54PM -, Perl6 RFC Librarian wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Objects: C pragma
>
> =head1 VERSION
>
> Maintainer: Damian Conway <[EMAIL PROTECTED]>
> Date: 14 September 2000
> Mail
On Mon, Sep 18, 2000 at 12:53:32PM -0400, Michael G Schwern wrote:
> On Mon, Sep 18, 2000 at 10:16:46AM -0400, John Porter wrote:
> > Hildo Biersma wrote:
> > > IMHO, mixing procedural and OO interfaces to the same module is a bad
> > > idea. Promoting it in the language is not wise.
> >
> > O.k
On Tue, Sep 19, 2000 at 07:29:56PM -, Perl6 RFC Librarian wrote:
> This RFC proposes a builtin C function, modelled after Graham Barr's
> C subroutine from builtin.pm
Please refer to List::Util rather than builtin.pm
the module name was changed as many did not like the name builting, as it
On Wed, Sep 20, 2000 at 07:06:21AM +1100, Damian Conway wrote:
>> >This RFC proposes that the internal cursor iterated by the C
>> >function be stored in the pad of the block containing the C,
>> >rather than being stored within the hash being iterated.
>>
>> Then how do you s
On Tue, Sep 19, 2000 at 03:23:30PM -0600, Tom Christiansen wrote:
> >> If the original list has no elements, C immediately throws an
> >> exception.
>
> >What do you mean by exception, die ? No other builtin dies like that at
> >runtime.
>
> Well, more can trigger run-time exceptions than peopl
On Wed, Sep 20, 2000 at 08:35:20AM +1100, Damian Conway wrote:
>> No other builtin dies like that at
>> runtime. Perhaps a return of undef would be more like other operators.
>
> That was my original proposal, but it was howled down by the
> mathematical elite, who vigorously insisted tha
On Tue, Sep 19, 2000 at 04:06:00PM -0600, Tom Christiansen wrote:
> Why not just check @numbers?
Well if the 'use trisate' pragma ever arises (did anyone RFC that ?)
$a = 1;
$b = undef;
$c = $a + $b;
$c is undef, not 1.
Graham.
On Tue, Sep 19, 2000 at 10:11:23PM -0700, Nathan Wiger wrote:
>undef null
>
>$a = undef; $a = null;
>$b = 1; $b = 1;
>$c = $a + b; $c = $a + $b;
>
>$c is 1
On Wed, Sep 20, 2000 at 12:00:05AM -0700, Russ Allbery wrote:
> Perl already has exactly the data value that you're looking for. This RFC
> is proposing to fix the wrong problem; the things that need to be changed
> (conditionally) are the logical operators, not the data value.
Absolutley, altho
On Wed, Sep 20, 2000 at 05:08:26AM -, Perl6 RFC Librarian wrote:
> =head1 ABSTRACT
>
> This RFC proposes a built-in C function, modelled after Graham
> Barr's C subroutine from the List::Utils module (a.k.a. The
> Module Formerly Known As builtin.pm).
:-)
> If fewer than N-1 elements would
On Wed, Sep 20, 2000 at 08:05:20AM -0400, Webmaster wrote:
> David Nicol Wrote in RFC 262:
> >foreach $item (@items){
> >#print "$item was at location ",$item:n,"\n";
> >print "$item was at location ${item:n}\n";
> >};
>
> What would really be nice here is an C function, similar to the
> scalar v
On Wed, Sep 20, 2000 at 09:03:39AM -0400, Webmaster wrote:
> Graham Barr Wrote:
> >Well if there ever is a way to shortcut grep this could be genera;ized
> >to
> >
> > my $index = grep { break if $_ eq $seek; 1 } @items;
>
> Wouldn't this also assume th
On Wed, Sep 20, 2000 at 08:30:44AM -0700, Nathan Wiger wrote:
> Using the proposed tristate pragma does not strike me as any better -
> in fact, worse - than adding null() because you are now changing the
> meaning of fundamental Perl operations. You're *still* introducing "yet
> another state of
On Wed, Sep 20, 2000 at 10:00:56AM -0700, Damien Neil wrote:
> On Wed, Sep 20, 2000 at 04:12:09AM -, Perl6 RFC Librarian wrote:
> > Add null() keyword and fundamental data type
>
> I think that this is better done as a special overloaded object used
> Incidentally, I'm surprised that DBI has
On Wed, Sep 20, 2000 at 10:08:09PM -0700, Glenn Linderman wrote:
> Russ Allbery wrote:
>
> > Why on earth would you want to do this in real code?
>
> I wouldn't, of course. This is just a demonstration that I want both
> semantics available concurrently.
If you are not going to use it, why imp
On Thu, Sep 21, 2000 at 03:38:50AM -0400, Michael G Schwern wrote:
> On Thu, Sep 21, 2000 at 03:54:27AM -, Perl6 RFC Librarian wrote:
> > =head1 IMPLEMENTATION
> >
> > Dunno. With my vague understanding of the existing code and hash
> > tables in general:
>
> I believe the main reason why ha
On Thu, Sep 21, 2000 at 03:38:59AM -0600, Tom Christiansen wrote:
> > > Could the prototype people please report whether Tim Bunce's issues with
> > > prototypes have been intentionally/adequately addressed?
>
> >I'm not a prototype person (in fact RFC 128 makes it a hanging offence
> >to us
On Thu, Sep 28, 2000 at 01:02:11PM -0500, Jonathan Scott Duff wrote:
> I thought I had sent this the other day, but it doesn't appear to have
> made it through...
>
> Here are a couple of ideas that I don't have time to RFC, but some who
> likes them might:
>
> 1. Allow the first argumen
On Mon, Oct 02, 2000 at 01:22:47PM -0600, Tom Christiansen wrote:
> > Eliott P. Squibb
> > Joe Blogg
>
> That is an excellent description of why THIS IS COMPLETE
> MADNESS.
It also shows how easy it is to get wrong
Graham.
On Mon, Oct 02, 2000 at 12:58:37PM -0700, Damien Neil wrote:
> What? I don't think people should be writing either XML or HTML
> as the source documentation format. I said that, quite clearly.
Then what are they going to write it in ? And don't tell me to get
some fangle dangled editor. Which w
This has been discussed on p5p many many times. And many times
I have agreed with what you wrote. However one thing you did not mention,
but does need to be considered is
func($x{1}{2}{3})
at this point you do not know if this is a read or write access as
the sub could do $_[0] = 'fred'. If th
On Tue, Feb 20, 2001 at 03:49:13AM +, Simon Cozens wrote:
> On Mon, Feb 12, 2001 at 01:58:35PM -0700, Tony Olekshy wrote:
> > Hi, it's me again, the guy who won't shut up about exception handling.
> > I'm trying,
>
> I'm catching.
And I'm thowing (up :)
Graham.
On Wed, Mar 28, 2001 at 09:13:01AM -0500, Mark-Jason Dominus wrote:
>
> > So you can say
> >
> > use Memoize;
> > # ...
> > memoize 'f';
> > @sorted = sort { my_compare(f($a),f($b)) } @unsorted
> >
> > to get a lot of the effect of the S word.
>
> Yes, and of course the inline version
On Thu, Apr 05, 2001 at 10:10:47PM +0100, Michael G Schwern wrote:
> > Then it might be easier to write modules that are testable without a test
> > driver. If you run the module directly, some distinguished block of code
> > could be executed that wouldn't be if the module were "included" via
>
On Fri, Apr 06, 2001 at 01:31:40PM +0200, Paul Johnson wrote:
> On Fri, Apr 06, 2001 at 10:01:47AM +0100, Graham Barr wrote:
>
> > unless (defined wantarray) {
> > # Self Test
> > }
> >
> > This works because whenever a file is use'd, require'
1 - 100 of 182 matches
Mail list logo
