Re: Objects, methods, attributes, properties, and other related frobnitzes

2003-02-22 Thread Graham Barr
On Fri, Feb 21, 2003 at 04:34:42PM -0500, Dan Sugalski wrote: > If A isa B, we certainly wouldn't want to call A's AUTOLOAD on a > method before we looked to see if B had a concrete instance of that > method. Right. The best you could probably do is note where you found the first AUTOLOAD so tha

Re: Objects and classes, try 3

2003-03-10 Thread Graham Barr
On Sun, Mar 09, 2003 at 02:08:02PM -0500, Dan Sugalski wrote: > At 1:52 PM -0500 3/9/03, Uri Guttman wrote: > > > "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: > > > > > > DS> * Objects have properties you can fetch and store by name > > DS> * Objects have methods you can call > > DS>

Re: Multimethod dispatch?

2003-06-03 Thread Graham Barr
On Mon, Jun 02, 2003 at 10:34:14AM -0600, Luke Palmer wrote: > What it seems you're wanting is it to be in the core. And I'm saying > that's irrelavent. There are thousands of great ideas out there, and > they can't all fit into Perl's core. That's why there's thousands of > modules on CPAN. H

DoD ordering (was Re: Timely object destruction)

2003-06-04 Thread Graham Barr
On Tue, Jun 03, 2003 at 07:24:04PM -0400, Benjamin Goldberg wrote: > IIRC, DoD normally happens something vaguely like this: > >for my $p (@all_pmcs) { > clear_is_live_flag($p); >} >our $traverse; >sub set_is_live_flag($p) { > if( !test_is_live_flag($p) and test_is_agre

Re: DoD ordering (was Re: Timely object destruction)

2003-06-04 Thread Graham Barr
On Wed, Jun 04, 2003 at 11:05:34AM +0200, Leopold Toetsch wrote: > Graham Barr <[EMAIL PROTECTED]> wrote: > > > I ask becasue what happens if an object actually wants > > to use its contents during its DESTROY ? > > > For example Net::POP3::DESTROY will send a r

Re: Testers & PASS

2003-08-07 Thread Graham Barr
On Monday, Aug 4, 2003, at 08:15 US/Pacific, Leon Brocard wrote: alian sent the following bits through the ether: But there is a serious problem with CPAN test database. There is like 100 000 reports in the CPAN db. This is not a big problem. 100_000 reports is a very small database and I still d

Re: Testers & PASS

2003-08-14 Thread Graham Barr
On Wed, 2003-08-13 at 12:30, Leon Brocard wrote: > http://dellah.org/testers/MIME-Lite-HTML gets the version sorting > wrong but "right". How do you sort, Iain? > > http://testers.cpan.org/search?request=dist&dist=MIME-Lite-HTML > keeps on timing out, so I don't know what it does. Graham? I just

Re: Testers & PASS

2003-08-14 Thread Graham Barr
On Wed, 2003-08-13 at 19:06, Leon Brocard wrote: > Graham Barr sent the following bits through the ether: > > > > Now maybe I should ignore the version numbers and instead sort using > > > the dates that the module was uploaded to CPAN, but that's external > > &

Re: Testers & PASS

2003-08-14 Thread Graham Barr
On Wed, 2003-08-13 at 17:20, Leon Brocard wrote: > Graham Barr sent the following bits through the ether: > > > > http://testers.cpan.org/search?request=dist&dist=MIME-Lite-HTML > > > keeps on timing out, so I don't know what it does. Graham? > > > >

Re: use English

2005-04-28 Thread Graham Barr
On Apr 27, 2005, at 6:39 AM, Aaron Sherman wrote: On Tue, 2005-04-26 at 10:48, Luke Palmer wrote: Aaron Sherman writes: The reasons I don't "use English" in P5: * Variable access is slower Hmm, looks to me like $INPUT_RECORD_SEPARATOR is faster. (Actually they're the same: on each run a di

Re: Open and pipe

2005-05-05 Thread Graham Barr
On May 4, 2005, at 8:13 AM, Uri Guttman wrote: AS> Why? Because IO::Socket.new takes parameters that are built out of its AS> entire inheritance tree, so a change to IO::Handle might radically AS> modify the signature of the constructor. makes sense. we should look at the p5 IO:: tree and

Re: The Pie-thon benchmark

2004-06-30 Thread Graham Barr
On 24 Jun 2004, at 21:49, Piers Cawley wrote: Dan Sugalski wrote: it's not exactly exciting watching two people hit return three times in front of a roomful of people. Although watching two people hit each other in the face with custard pies three times in front of a roomful of people may be a lot

Re: Return with no expression

2004-08-24 Thread Graham Barr
On 24 Aug 2004, at 22:14, Aaron Sherman wrote: You don't HAVE to use auto-topicalization. You CAN always write it long-hand if you find that confusing: for @words -> $word { given ($chars($word) > 70) -> $toolong { say abbreviate($word) ?? $word;

Re: [Devel::Cover] @INC at Runtime?

2004-09-17 Thread Graham Barr
On 17 Sep 2004, at 15:48, Ricardo SIGNES wrote: * David Wheeler <[EMAIL PROTECTED]> [2004-09-17T00:51:22] So, what's to be lost by having the inc directories default to the contents of @INC when you load Devel::Cover rather than at install time? Presumably the problem is that by runtime, lib and bl

Re: flex perl mess

2001-10-24 Thread Graham Barr
On Wed, Oct 24, 2001 at 09:06:14AM -0400, Aaron Sherman wrote: > On Tue, Oct 23, 2001 at 02:53:19PM +0200, Nadim Khemir wrote: > > > > Don't we already have that in Perl 5? > > > > > > if ( /\G\s+/gc ) {# whitespaces } > > >elsif ( /\G[*/+-]/gc ) { # operator } > > >elsif (

Re: Apropos of nothing...

2001-12-13 Thread Graham Barr
On Fri, Dec 14, 2001 at 06:39:02AM +1100, Damian Conway wrote: > >> In the following code fragment, what context is foo() in? >> >> @ary[0] = foo() > > Scalar context. @ary[0] is a single element of @ary. > > To call foo() in list context use any of the following: > > (@

Re: Some random design notes

2002-01-09 Thread Graham Barr
On Tue, Jan 08, 2002 at 06:38:02PM -0500, Dan Sugalski wrote: > ># Attributes are done as a hash of hashes. Each interpreter has a > ># pointer to an attribute hash, whose keys are the attribute names. The > ># values will be hash pointers. Those hashes will each have a key which > ># is a PMC poi

Re: on parrot strings

2002-01-19 Thread Graham Barr
I belive IBM use inversion lists in thier ICU library for sets of unicode characters. Graham. On Sat, Jan 19, 2002 at 07:08:25PM +0200, Jarkko Hietaniemi wrote: > Honour where honour is due: I've got some questions about inversion > lists. Where I saw them mentioned by that name were some draft

Re: [A-Z]+\s*\{

2002-01-20 Thread Graham Barr
On Sun, Jan 20, 2002 at 05:29:39AM -0800, Damian Conway wrote: > On Saturday 19 January 2002 22:05, Brent Dax wrote: > > > Is this list of special blocks complete and correct? > > Close and close. As of two days ago, Larry's thinking was: > > BEGIN Executes at the beginning of co

Re: Apoc4: The loop keyword

2002-01-21 Thread Graham Barr
On Mon, Jan 21, 2002 at 12:50:38PM -0800, Larry Wall wrote: > : What's the chance that it could be considered so? > > In most other languages, you wouldn't even have the opportunity to put > a declaration into the conditional. You'd have to say something like: > > my $line = <$in>; >

Re: Apoc4: The loop keyword

2002-01-21 Thread Graham Barr
On Mon, Jan 21, 2002 at 03:58:49PM -0500, Michael G Schwern wrote: > On Mon, Jan 21, 2002 at 03:43:07PM -0500, Damian Conway wrote: > > Casey wrote: > > > > > So you're suggesting that we fake lexical scoping? That sounds more > > > icky than sticking to true lexical scoping. A block dictates s

Re: Apoc4: The loop keyword

2002-01-21 Thread Graham Barr
On Mon, Jan 21, 2002 at 01:01:09PM -0800, Larry Wall wrote: > Graham Barr writes: > : But are we not at risk of introducing another form of > : > : my $x if 0; > : > : with > : > : if my $one = { > : ... > : } > : elsif my $two

Re: Apoc4: The loop keyword

2002-01-21 Thread Graham Barr
On Mon, Jan 21, 2002 at 01:38:39PM -0800, Larry Wall wrote: > Graham Barr writes: > : On Mon, Jan 21, 2002 at 01:01:09PM -0800, Larry Wall wrote: > : > Graham Barr writes: > : > : But are we not at risk of introducing another form of > : > : > : > : my

Re: Some Apocalypse 4 exception handling questions.

2002-01-23 Thread Graham Barr
On Wed, Jan 23, 2002 at 02:25:35PM -0800, Glenn Linderman wrote: > I think you just said the same thing I did. To be more explicit, using > the terminology you seem to want to use, I'll point out that I was only > talking about the case of an inherited method, not a _replacement_ > method. In ot

Re: parrot rx engine

2002-01-30 Thread Graham Barr
On Wed, Jan 30, 2002 at 09:32:49AM -0800, Brent Dax wrote: > # rx_setprops P0, "i", 2 > # branch $start0 > # $advance: > # rx_advance P0, $fail > # $start0: > # rx_literal P0, "a", $advance > # > # First, we set the rx

Re: parrot rx engine

2002-01-31 Thread Graham Barr
On Thu, Jan 31, 2002 at 08:54:21AM -0800, Brent Dax wrote: > Peter Haworth: > # On Wed, 30 Jan 2002 17:45:58 +, Graham Barr wrote: > # > On Wed, Jan 30, 2002 at 09:32:49AM -0800, Brent Dax wrote: > # > > # rx_setprops P0, "i", 2 > # &g

Re: parrot rx engine

2002-01-31 Thread Graham Barr
On Thu, Jan 31, 2002 at 11:18:58AM -0800, Hong Zhang wrote: > > Because parts of an rx can be case-insensitive while other parts > > are case-sensitive, we will probably need two sorts of ops anyway > > (or a way to tell the op to be case-insensitive). And you will > > only be able to do the case

Re: PMCs, setting, and suchlike things

2002-02-14 Thread Graham Barr
On Thu, Feb 14, 2002 at 02:10:20PM +, Dave Mitchell wrote: > 2. If so, how do we distinguish between two PMCs, both of whose > vtable pointers currently point to the 'Dog' vtable, but one of whom has > been delared as type Dog and so should never have it's vatble pointer > updated, and the oth

Re: Unary dot

2002-04-10 Thread Graham Barr
On Wed, Apr 10, 2002 at 01:35:22PM -0400, Mark J. Reed wrote: > On Wed, Apr 10, 2002 at 10:30:25AM -0700, Glenn Linderman wrote: > > method m1 > > { > >m2; # calls method m2 in the same class > Yes, but does it call it as an instance method on the current invocant > or as a class method with

Re: How to default? (was Unary dot)

2002-04-12 Thread Graham Barr
On Fri, Apr 12, 2002 at 09:26:45AM +0100, Piers Cawley wrote: > Trey Harris <[EMAIL PROTECTED]> writes: > > > I think I've missed something, even after poring over the archives for > > some hours looking for the answer. How does one write defaulting > > subroutines a la builtins like print() and

Re: // in Perl 5.8?

2002-04-17 Thread Graham Barr
On Wed, Apr 17, 2002 at 01:09:43PM -0700, David Wheeler wrote: > Anyone know what the chances are that some enterprising C hacker > can/will/did get the // and //= operator into Perl 5.8? Seems like it > wouldn't be a huge deal to add, and I'd love to have it sooner rather than > later. It is not

Re: // in Perl 5.8?

2002-05-01 Thread Graham Barr
On Wed, May 01, 2002 at 12:17:52PM -0700, David Wheeler wrote: > On 5/1/02 12:11 PM, "Brent Dax" <[EMAIL PROTECTED]> claimed: > > > It's far too late to make it into 5.8, but it looks like it'll be in > > 5.10 when that comes out (in a year or two). > > I figured. Too bad. ;-) A year or two is l

Re: // in Perl 5.8?

2002-05-01 Thread Graham Barr
On Wed, May 01, 2002 at 01:53:24PM -0700, Brent Dax wrote: > Graham Barr: > # On Wed, May 01, 2002 at 12:17:52PM -0700, David Wheeler wrote: > # > On 5/1/02 12:11 PM, "Brent Dax" <[EMAIL PROTECTED]> claimed: > # > > # > > It's far too late to make

FIRST, BETWEEN, etc.. (was Re: Loop controls)

2002-05-07 Thread Graham Barr
I have been following this thread, but I would just like to inject a summary of the various related UPPERCASE blocks PREExecutes on block entry. Loop variables are in a known state POST Executes on block exit. Loop variables are in a known state NEXT Executes on impli

Re: FIRST, BETWEEN, etc.. (was Re: Loop controls)

2002-05-07 Thread Graham Barr
On Tue, May 07, 2002 at 12:27:08PM -0500, Allison Randal wrote: > On Tue, May 07, 2002 at 03:15:48PM +0100, Graham Barr wrote: > > > > LAST Executes on implicit loop exit or call to last() > > Loop variables may be unknown > > Not exactly "unknown".

Re: Copy-on-write strings

2002-05-10 Thread Graham Barr
On Fri, May 10, 2002 at 12:12:41PM -0400, Dan Sugalski wrote: > At 5:38 PM +0200 5/10/02, Peter Gibbs wrote: > >The result is that the last header of a COWed string will still believe that > >the buffer is shared until a GC collection run occurs, and therefore could > >result in buffers being copi

Re: How to implement both object->method and module::function interface?

2000-08-16 Thread Graham Barr
On Tue, Aug 15, 2000 at 04:59:19PM -0800, Michael Fowler wrote: > Which makes me think of the following. You don't need to 'use' a seperate > module for a procedural or OO interface. The module author could simply > provide a constructor in the procedural module that would require the OO > modul

Re: How to implement both object->method and module::function interface?

2000-08-16 Thread Graham Barr
On Tue, Aug 15, 2000 at 12:33:15PM +0100, Tim Bunce wrote: > I don't think you can make much valuable progress down that road till > we know what Larry's thinking about how to support multiple installed > versions of a module and multiple implementations of the same 'interface'. I think much of t

Re: How to implement both object->method and module::function interface?

2000-08-16 Thread Graham Barr
On Tue, Aug 15, 2000 at 03:17:36PM -0400, Chaim Frenkel wrote: > >>>>> "GB" == Graham Barr <[EMAIL PROTECTED]> writes: > > GB> On Tue, Aug 15, 2000 at 10:14:36AM -0400, Chaim Frenkel wrote: > >> As much as I'm not for it, would > >&g

Re: "Try? There is no try." -- Yoda's Exception handling syntax

2000-08-16 Thread Graham Barr
On Tue, Aug 15, 2000 at 08:11:55PM +, David L. Nicol wrote: > Would someone please enlighten me as to the purpose of an explicit "try." In my mind it allows the important code to come before the "oh crap something went wrong" code. Graham.

Re: English language basis for "throw"

2000-08-16 Thread Graham Barr
On Wed, Aug 16, 2000 at 10:11:32AM -0400, Chaim Frenkel wrote: > > "TO" == Tony Olekshy <[EMAIL PROTECTED]> writes: > > TO> Consider "finally" vs. "always". Always? Even if force majeur? > TO> Finally simply means, "as the final act of the unwind processing". > > Am I missing something. I

Re: Towards a reasonable unwinding flow-control semantics.

2000-08-16 Thread Graham Barr
On Wed, Aug 16, 2000 at 10:19:53AM -0400, Chaim Frenkel wrote: > I would say that outside of the try block all throws are caught if > at all by the wrapping try. So that throws propogate outward. Never > back within itself. Agreed. > There is one case to be considered, what if the try block wish

Re: Make lvalue subs the default (was Re: RFC 107 (v1) lvalue subs should receive the rvalue as an argument)

2000-08-16 Thread Graham Barr
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 >

Re: RFC 30 (v2) STDIN, STDOUT, and STDERR should be renamed

2000-08-16 Thread Graham Barr
On Wed, Aug 16, 2000 at 08:27:04PM +, Nick Ing-Simmons wrote: > Perl6 Rfc Librarian <[EMAIL PROTECTED]> writes: > > > >In addition, this RFC recommends deprecating select(), since it is no > >longer needed with the new fileobject approach described in RFC 14. > > > > > > $oldoutput = select(

Re: Towards a reasonable unwinding flow-control semantics.

2000-08-16 Thread Graham Barr
On Wed, Aug 16, 2000 at 01:16:26AM -0600, Tony Olekshy wrote: > try { } finally { } catch { } I don not see ht epoint of this ? IMO, it should be simple. try { } catch Class { } catch { } finally { } If try throws it is caught by the catch blocks finally is always run if any of

Re: RFC 120 (v1) Implicit counter in C statements, possibly C<$#>.

2000-08-16 Thread Graham Barr
On Wed, Aug 16, 2000 at 11:42:20AM -1000, Tim Jenness wrote: > What about: > > for (0..$#array) { > print $array[$i], " is at index ", $i, "\n"; > } > > I use that whenever I need to loop over indices of two arrays at once. And with the proposed zip() you may be able to do so

Re: RFC 111 (v1) Whitespace and Here Docs

2000-08-16 Thread Graham Barr
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

Re: RFC 109 (v1) Less line noise - let's get rid of @%

2000-08-16 Thread Graham Barr
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.

Re: error handling and syntax extension

2000-08-16 Thread Graham Barr
On Wed, Aug 16, 2000 at 04:49:15PM -0500, David L. Nicol wrote: > > > or AUTOLOAD can be defined in terms of C > and overloaded that way, rather than being its own > kind of magic. > > catch "AUTOLOAD-$classname-$polymorphicsignature" {... But why should I have to know that a sub I want

Re: RFC 63 (v3) Exception handling syntax

2000-08-16 Thread Graham Barr
On Tue, Aug 15, 2000 at 04:39:24PM -0700, Peter Scott wrote: > >PRL> =head2 Exception classes - ignoring > > > >PRL> Note that we could also make it possible to selectively or globally > >ignore > >PRL> exceptions, so that perl continues executing the line after the C > >PRL> statement. Just imp

Re: ANNOUNCE: Inline 0.23 (Mix Perl and C w/o XS)

2000-08-17 Thread Graham Barr
On Thu, Aug 17, 2000 at 05:26:18PM -0400, Sam Tregar wrote: > On Thu, 17 Aug 2000, Nick Ing-Simmons wrote: > > Simon Cozens <[EMAIL PROTECTED]> writes: > > >Wow. I'm sold. Can this be how we should be doing XS in Perl 6? > > So we now run equivalent of xsubpp and cc every time script is run? > >

Re: RFC 128 (v1) Subroutines: Extend subroutine contexts to include name parameters and lazy arguments

2000-08-18 Thread Graham Barr
On Fri, Aug 18, 2000 at 06:04:55PM +1000, Damian Conway wrote: >> > An argument would be associated with a named parameter by >> > prefixing it with a standard Perl label (i.e. an identifier-colon >> > sequence). For example: >> > >> > @mapped = doublemap(args: @list,

Re: RFC 118 (v1) lvalue subs: parameters, explicit assignment, and wantarray() changes

2000-08-17 Thread Graham Barr
On Thu, Aug 17, 2000 at 07:04:40PM +0200, Johan Vromans wrote: > And, what would the lvalue routine return? Currently, $a = $b = $c > implies that both $b and $a get the value $c. But with lvalue subs I > can write something like > > yech($foo) = $bar > > that assigns $bar to $foo, and retu

Re: RFC 118 (v1) lvalue subs: parameters, explicit assignment, and wantarray() changes

2000-08-17 Thread Graham Barr
On Fri, Aug 18, 2000 at 12:25:42AM -0400, Chaim Frenkel wrote: > As Graham pointed out, is an lvalue sub supposed to act like a tie or > like a variable. Both. As Damian points out the lvalue sub must return something that can be used as an lvalue. Normal assignment hen happens. So the result w

Re: RFC 118 (v1) lvalue subs: parameters, explicit assignment, and wantarray() changes

2000-08-17 Thread Graham Barr
On Thu, Aug 17, 2000 at 05:10:40PM -0400, Buddha Buck wrote: > SO what you are saying is that the proper execution of "$p->foo(@args) += > $val;" should be (equivalent to): > > 1. Evaluate $val and get an rvalue $rval. > 2. Evaluate $p->foo(@args) and get an lvalue $lfoo. The order of those tw

Re: RFC 120 (v2) Implicit counter in for statements, possibly $#.

2000-08-20 Thread Graham Barr
On Sat, Aug 19, 2000 at 09:23:03AM -0400, Ken Fox wrote: > "Christopher J. Madsen" wrote: > > foreach $item $index (@array) { > > print $item, " is at index ", $index, "\n"; > > } > > That's useful syntax, but I'd rather it mean stepping > pair-wise through @array. Then we could scan

Re: RFC 88: What does catch "Foo" { } do?

2000-08-20 Thread Graham Barr
On Fri, Aug 18, 2000 at 11:04:03PM -0600, Tony Olekshy wrote: > As currently promulgated, catch "Foo" {} will always catch, > because "Foo" is true. Will this cause confusion for developers > who meant to say catch Foo {}? And what happens when someone > says catch "Foo", "Bar" {}? > > We can't

Re: RFC 110 (v1) counting matches

2000-08-16 Thread Graham Barr
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

Re: RFC 110 (v1) counting matches

2000-08-16 Thread Graham Barr
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

Re: RFC for $ME class variable (was Re: RFC 124 (v1) Sort order for any hash)

2000-08-20 Thread Graham Barr
On Sat, Aug 19, 2000 at 09:32:50AM -0700, Randal L. Schwartz wrote: > > "John" == John Siracusa <[EMAIL PROTECTED]> writes: > > John> I don't like $ME either, but my alternative is probably even more > John> blasphemous: use $self. "It usurps a variable name that has been legal for > John> c

Re: RFC 88: What does catch "Foo" { } do?

2000-08-24 Thread Graham Barr
On Sun, Aug 20, 2000 at 09:23:20AM -0700, Peter Scott wrote: > At 10:14 AM 8/20/00 -0600, Tony Olekshy wrote: > >Graham Barr wrote: > > > > > > I am of the opinion that only a class name should follow catch. > > > If someone wants to catch ba

Re: Multiple for loop variables

2000-08-28 Thread Graham Barr
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

Re: RFC 175 (v1) Add C keyword to force list context (like C)

2000-09-01 Thread Graham Barr
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

Re: RFC 175 (v1) Add C keyword to force list context (like C)

2000-08-31 Thread Graham Barr
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.

Re: Change "($one, $two)=" behavior for optimization? (was Re: RFC 175 (v1) Add C keyword toforce list context (like C))

2000-09-05 Thread Graham Barr
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'

Re: RFC 189 (v1) Objects : Hierarchical calls to initializersanddestructors

2000-09-04 Thread Graham Barr
On Mon, Sep 04, 2000 at 11:09:18AM +0100, Piers Cawley wrote: > Damian Conway <[EMAIL PROTECTED]> writes: > > >> But I've gotta nitpick the name. I wonder if BLESS wouldn't be better? > >> print calls PRINT, printf calls PRINTF, even if the subs don't do any > >> printing. Sure makes

Re: RFC 193 (v1) Objects : Core support for method delegation

2000-09-05 Thread Graham Barr
On Mon, Sep 04, 2000 at 09:53:39PM -, Perl6 RFC Librarian wrote: > The proposed delegation mechanism would work via a pragma: > > use delegation > attr1 => [qw( method1 method2 method3 )], > attr2 => [qw( method4 method5 )], > attr3 => [], >

Re: $a in @b

2000-09-06 Thread Graham Barr
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.) >

Re: Exceptions and Objects

2000-08-15 Thread Graham Barr
On Tue, Aug 15, 2000 at 11:47:03AM -0500, Jonathan Scott Duff wrote: > On Tue, Aug 15, 2000 at 11:47:32AM +0100, Graham Barr wrote: > > On Mon, Aug 14, 2000 at 10:56:36AM -0500, Jonathan Scott Duff wrote: > > > try { } > > > catch SomeException { } >

Re: $a in @b

2000-09-08 Thread Graham Barr
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

Re: perl 5.6.0 stdlib stats

2000-09-11 Thread Graham Barr
This is very much what I had started to do, although you have already taken it further that what I had done. However I was also lookiing at documentation style. Here are just a selection of different ways to document a function or method =item timeit(COUNT, CODE) =item timethis ( COUNT, CODE

Re: perl 5.6.0 stdlib stats

2000-09-11 Thread Graham Barr
On Mon, Sep 11, 2000 at 06:37:26AM -0600, Tom Christiansen wrote: > >> Alongside giving consistent APIs I think perl6 should also give consistent > >> documentation format. > > >Are there any proposals to add per-argument markup to POD so that these > >could be generated automatically? (Even in t

Re: RFC 223 (v1) Objects: C pragma

2000-09-15 Thread Graham Barr
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

Re: RFC 212 (v1) Make length(@array) work

2000-09-13 Thread Graham Barr
On Wed, Sep 13, 2000 at 08:32:08AM -0700, Randal L. Schwartz wrote: > > "Perl6" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes: > > Perl6> Make length(@array) work > > Perl6> I propose to make length() return the number of elements in the array > Perl6> it is passed, if its first argument

Re: Draft RFC: new pragma: C

2000-09-14 Thread Graham Barr
I would suggest that anyone want to contribute to this discussion should first read the thread about the addition of this pragma to perl5 in the perl5-porters archives http://www.xray.mpe.mpg.de/cgi-bin/w3glimpse/perl5-porters?query=use+namespace+pragma&errors=0&case=on&maxfiles=100&maxlines=30

Re: $a in @b (RFC 199)

2000-09-12 Thread Graham Barr
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

Re: RFC 224 (v1) Objects : Rationalizing C, C, and C

2000-09-19 Thread Graham Barr
On Mon, Sep 18, 2000 at 08:54:30AM -0600, Tom Christiansen wrote: > >This RFC proposes that rather than three separate mechanisms (in three > >separate namespaces) to determine object typing information, Perl 6 > >simply extend the C function to return all the necessary > >information in a list co

Re: RFC 228 (v2) Add memoize into the standard library

2000-09-19 Thread Graham Barr
On Tue, Sep 19, 2000 at 06:57:07AM -, Perl6 RFC Librarian wrote: > =head1 OUTSTANDING ISSUES > > A few people mentioned that using memoize() as a function has some > action-at-a-distance qualities, although it is useful for caching > builtin functions such as cos() and sin(). But those co

Re: RFC 260 (v1) More modules

2000-09-19 Thread Graham Barr
I would suggest looking at the SDK that is being developed for perl5. In fact I would suggest that is probbaly the way to go, a small-ish core and various SDK's targeted towards different areas. As many of these modules are maintained by separate authors, haveing a separate SDK will allow a diff

Re: RFC 263 (v1) Add null() keyword and fundamental data type

2000-09-20 Thread Graham Barr
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

Re: RFC 263 (v1) Add null() keyword and fundamental data type

2000-09-20 Thread Graham Barr
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

Re: RFC 76 (v3) Builtin: reduce

2000-09-20 Thread Graham Barr
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

Re: RFC 262 (v1) Index Attribute

2000-09-20 Thread Graham Barr
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

Re: RFC 262 (v1) Index Attribute

2000-09-20 Thread Graham Barr
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

Re: RFC 263 (v1) Add null() keyword and fundamental data type

2000-09-20 Thread Graham Barr
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

Re: RFC 263 (v1) Add null() keyword and fundamental data type

2000-09-21 Thread Graham Barr
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

Re: RFC 266 (v1) Any scalar can be a hash key

2000-09-21 Thread Graham Barr
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

Re: Beefier prototypes (was Re: Multiple for loop variables)

2000-09-21 Thread Graham Barr
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

Re: RFC 76 (v2) Builtin: reduce

2000-09-19 Thread Graham Barr
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

Re: RFC 76 (v2) Builtin: reduce

2000-09-19 Thread Graham Barr
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

Re: RFC 76 (v2) Builtin: reduce

2000-09-19 Thread Graham Barr
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

Re: RFC 255 (v2) Fix iteration of nested hashes

2000-09-19 Thread Graham Barr
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

Re: RFC 223 (v1) Objects: C pragma

2000-09-19 Thread Graham Barr
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

Re: RFC 263 (v1) Add null() keyword and fundamental data type

2000-09-20 Thread Graham Barr
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

Re: Temporal changes

2009-02-24 Thread Graham Barr
On Feb 23, 2009, at 3:56 PM, mark.a.big...@comcast.net wrote: Instant Moment Point PointInTime Timestamp Event Jiffy Time Juncture

Re: Dallas.p6m

2009-03-19 Thread Graham Barr
On Mar 18, 2009, at 5:26 PM, fREW Schmidt wrote: s1n and I decided that we would start Dallas.p6m as we are close to each other geographically speaking. We are meeting tomorrow (Thursday, March 19, 7:00PM) at a coffee shop with free wifi. The address is 985 W Bethany Dr Allen, TX 75013.

<    1   2