vote no - Re: Unicode operators [Was: Re: UTF-8 and Unicode FAQ, demos]

The first message had many of the following characters viewable in my telnet window, but the repost introduced a 0xC2 prefix to the 0xA7 character. I have this feeling that many people would vote against posting all these funny characters, as is does make reading the perl6 mailing lists difficult

[CVS ci] string_set is back for a faster live - not only

As suggested by Brent, string_set gives us a big improvement, where strings are heavily used. One examples is life.pasm, where the generate loop does: substr S0, S15, I3, 1 ~10^6 times. Till now, S0 (the result of substr) was constructed every time, now it get's just reused. This improves lif

Re: [perl #18219] on_exit not portable

Josh Wilmes wrote: I agree. However, the point is fairly moot.. If we're going to do a Parrot_on_exit, it's just as easy to provide our own Parrot_exit and not need atexit() either.. it's not like atexit() is giving us much at that point. which would mean, that internal_exception ne

This weeks Perl 6 summary

The Perl 6 Summary for the week ending 20021103 Welcome to the latest of the ongoing series of Perl 6 summaries, in which your arrogant moderator does battle with the forces of prolixity in a Brobdingnagian attempt to tame the tortuously tangled threads of Perl 6's design and develo

Re: This weeks Perl 6 summary

[EMAIL PROTECTED] (Piers Cawley) writes: > * Superpositional operators will be too rare to justify giving them > precious one character operators. I don't think I think that they'd be too rare. (I think) But I do think that we're overinflating their importance. Changing the way peopl

Re: [PATCH?] default char type

Dan Sugalski wrote: At 1:18 PM +0200 10/26/02, Leopold Toetsch wrote: The default chartype (e.g. for string constants in PBC) is currently unicode with utf32 encoding. Can someone comment on this? In some debug sessions I saw a lot of string_compare -> string_transcode cased by this default

Re: This weeks Perl 6 summary

On Wed 06 Nov, Piers Cawley wrote: > miniparrot, a first attempt > If you've been paying attention to the Parrot build process, you'll be > aware that it was always a goal to use a cut down variant of parrot > itself to run the configuration tests. The plan is that this miniparrot >

[FYI] life generations

Here some numbers for examples/assembly/life.pasm (generations/sec) on my Athlon 800 i386/linux: 314 24th Sept 2002 CGoto/no optimization 374 trace_system_stack, lo_var_ptr 401 string_substr/_compare 587 string_set 755 -O3 (except core_ops_cg w/o opt.) 910 -O3 -g (fast_core) 997 -O

Re: [CVS ci] string_set is back for a faster live - not only

Leopold Toetsch wrote: [ substr in life.pasm ] ~10^6 times. 10^7 set S0, S1 { $1 = $2 } would become string_set(interpreter, $1, $2) Exactly this example is wrong, because here these 2 registers just point to the same string. leo

Re: [CVS ci] string_set is back for a faster live - not only

Leopold Toetsch wrote: > string_set is currently only used in string_substr, but, when people are > ok with this, can be used everywhere in core.ops, where a string > register is globbered. The behaviour of the following program has changed, is this correct? set S0, "test" set S1, S0 set

Keyword arguments

So, I was, thinking about the way Common Lisp handles keyword arguments. It's possible to declare a Lisp function as follows: (defun make-para ( content &key alignment font size color ) ...) The point here is that the first argument is dealt with positionally, and subsequent, optional args ar

Re: [CVS ci] string_set is back for a faster live - not only

Peter Gibbs wrote: Leopold Toetsch wrote: string_set is currently only used in string_substr, but, when people are ok with this, can be used everywhere in core.ops, where a string register is globbered. The behaviour of the following program has changed, is this correct? set S0, "test"

Superpositions and laziness

It occurred to me that being able to set up 'pure' functions in such a way that they are lazily evaluated when passed a superposition might be a win. And then I got to thinking about what would be required from the language to allow me to implement this functionality in a module. I am assuming (fo

Re: Keyword arguments

I think Damian already covered this: it's the semicolon. sub mysub(String $content; int $key, int $align) { ... } sub callmysub { mysub("Testing .. 1, 2, 3!"; key => 1024, align => Module::RIGHT); } Which, upon reflection, apparently introduces an "implicit hashparsing" context for autoquotin

Back from Seattle

Okay, I'm back, and over the next few days I'll be digging through the week's backlog of mail. I do apologize--I assumed I'd have reasonable network access but, alas, that wasn't the case. -- Dan --"it's like this"--

Re: Draft sketch of bytecode generation

At 10:17 PM + 10/30/02, Kv Org wrote: On Tue, 29 Oct 2002 09:55:23 -0800, Chromatic wrote: I'd really like to be able to save comments from source files as metadata. This has at least two potential benefits. First, it >makes it much easier to recreate the whole file from bytecode (especiall

Re: [perl #18127] [PATCH] Implicit stack direction probe

At 9:03 AM +0100 11/5/02, Leopold Toetsch wrote: Dan Sugalski wrote: At 9:41 AM +0100 10/30/02, Leopold Toetsch wrote: Jason Gloudon wrote: ... By default both compilers align stack variables at their natural alignment, so PMC pointers would normally fall on 4 byte boundaries. So, this "s

Re: Keyword arguments

> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm > From: Piers Cawley <[EMAIL PROTECTED]> > Date: Wed, 06 Nov 2002 12:44:39 + > X-SMTPD: qpsmtpd/0.12, http://develooper.com/code/qpsmtpd/ > > So, I was, thinking about the way Common Lisp handles keyword > arguments. It's possible to decl

Re: Keyword arguments

Austin Hastings said: > sub callmysub > { > mysub("Testing .. 1, 2, 3!"; key => 1024, align => Module::RIGHT); > } > > Which, upon reflection, apparently introduces an "implicit hashparsing" > context for autoquoting hashkeys. Those are pairs, aren't they? -- Paul Johnson - [EMAIL PROTECTED]

list comprehensions

Will there be some shorter-hand way to say these? @a = @grades[grep $_ >= 90, @grades]; @b = @grades[grep 80 <= $_ < 90, @grades]; @c = @grades[grep 70 <= $_ < 80, @grades]; Granted, it's fairly compact as it is but I'm wondering if there's some way to not have to mention

Re: list comprehensions

On 2002-11-06 at 11:43:20, Jonathan Scott Duff wrote: > > Will there be some shorter-hand way to say these? > > @a = @grades[grep $_ >= 90, @grades]; > @b = @grades[grep 80 <= $_ < 90, @grades]; > @c = @grades[grep 70 <= $_ < 80, @grades]; I think what you mean here is just

Re: Keyword arguments

"Paul Johnson" <[EMAIL PROTECTED]> writes: > Austin Hastings said: > >> sub callmysub >> { >> mysub("Testing .. 1, 2, 3!"; key => 1024, align => Module::RIGHT); >> } >> >> Which, upon reflection, apparently introduces an "implicit hashparsing" >> context for autoquoting hashkeys. > > Those are p

Re: list comprehensions

On Wed, Nov 06, 2002 at 12:54:12PM -0500, Mark J. Reed wrote: > > On 2002-11-06 at 11:43:20, Jonathan Scott Duff wrote: > > > > Will there be some shorter-hand way to say these? > > > > @a = @grades[grep $_ >= 90, @grades]; > > @b = @grades[grep 80 <= $_ < 90, @grades]; > > @c = @gra

Re: list comprehensions

Jonathan Scott Duff <[EMAIL PROTECTED]> writes: > Will there be some shorter-hand way to say these? > > @a = @grades[grep $_ >= 90, @grades]; > @b = @grades[grep 80 <= $_ < 90, @grades]; > @c = @grades[grep 70 <= $_ < 80, @grades]; > > Granted, it's fairly compact as it is but I'

Re: list comprehensions

[EMAIL PROTECTED] (Piers Cawley) writes: > I confess I never quite understood why the python folks were so proud > of list comprehensions, AFAICT they're just 'grep' and 'map' given > fancy descriptions. Well, sort of. They're more like this: @array[grep { func() } 0..$#array] -- "If you

Re: Should memory be washed?

At 10:03 AM +0100 11/5/02, Leopold Toetsch wrote: Peter Gibbs wrote: What is the official position with respect to laundry services in the Parrot memory allocation code? I would strongly urge for calloc()ed memory as done now. This is one place where the current copying scheme is a win--we

Re: [perl #18219] on_exit not portable

At 7:58 on 11/06/2002 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Josh Wilmes wrote: > > > > I agree. However, the point is fairly moot.. If we're going to do a > > Parrot_on_exit, it's just as easy to provide our own Parrot_exit and not > > need atexit() either.. it's not like atex

Re: [perl #18219] on_exit not portable

At 1:31 PM -0500 11/6/02, Josh Wilmes wrote: At 7:58 on 11/06/2002 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote: Josh Wilmes wrote: > I agree. However, the point is fairly moot.. If we're going to do a > Parrot_on_exit, it's just as easy to provide our own Parrot_exit and not > need

Re: [perl #18219] on_exit not portable

At 13:41 on 11/06/2002 EST, Dan Sugalski <[EMAIL PROTECTED]> wrote: > Well, I got bit this week by the on_exit stuff. I'm still not sure > why we need this. Could someone please explain, so I don't have to > yank it out? Leo said: > The on_exit/atexit is currently necessary to clean up behind

Re: [perl #18219] on_exit not portable

At 1:47 PM -0500 11/6/02, Josh Wilmes wrote: At 13:41 on 11/06/2002 EST, Dan Sugalski <[EMAIL PROTECTED]> wrote: Well, I got bit this week by the on_exit stuff. I'm still not sure why we need this. Could someone please explain, so I don't have to yank it out? Leo said: The on_exit/atexit

Re: [perl #18219] on_exit not portable

At 13:55 on 11/06/2002 EST, Dan Sugalski <[EMAIL PROTECTED]> wrote: > >Leo said: > > > >> The on_exit/atexit is currently necessary to clean up behind exceptions. > >> If you don't mind memory leaks after exceptions, remove the > > Right, I saw that, I just don't understand why. If it's in as a

Re: [FYI] life generations

At 12:52 PM +0100 11/6/02, Leopold Toetsch wrote: Here some numbers for examples/assembly/life.pasm (generations/sec) on my Athlon 800 i386/linux: 314 24th Sept 2002 CGoto/no optimization 374 trace_system_stack, lo_var_ptr 401 string_substr/_compare 587 string_set 755 -O3 (except core

Re: [CVS ci] string_set is back for a faster live - not only

At 2:13 PM +0100 11/6/02, Leopold Toetsch wrote: Peter Gibbs wrote: Leopold Toetsch wrote: string_set is currently only used in string_substr, but, when people are ok with this, can be used everywhere in core.ops, where a string register is globbered. The behaviour of the following program

Re: Draft sketch of bytecode generation

If memory serves me right, Dan Sugalski wrote: > (Parrot bytecode is inherently unverifiable as well, at least in > the general case, which exacerbates the problem) Hmm... Why ? ... Loose typing ? Or does it just become an undecidability problem ?... Gopal -- The difference between insanit

Re: [perl #18219] on_exit not portable

Dan Sugalski wrote: At 1:47 PM -0500 11/6/02, Josh Wilmes wrote: At 13:41 on 11/06/2002 EST, Dan Sugalski <[EMAIL PROTECTED]> wrote: Well, I got bit this week by the on_exit stuff. I'm still not sure why we need this. Could someone please explain, so I don't have to yank it out? Leo sai

Re: Should memory be washed?

Dan Sugalski wrote: I don't have a problem with guaranteeing zeroed memory, but it's not free. If we're going with a malloc-style allocator then I explicitly do *not* want to give guarantees of zeroed memory. It doesn't make much sense to give Parrot_{re,}alloc different semantics depending

Re: list comprehensions

Jonathan Scott Duff wrote: On Wed, Nov 06, 2002 at 12:54:12PM -0500, Mark J. Reed wrote: On 2002-11-06 at 11:43:20, Jonathan Scott Duff wrote: Will there be some shorter-hand way to say these? @a = @grades[grep $_ >= 90, @grades]; @b = @grades[grep 80 <= $_ < 90, @grades]; @c = @grades[gre

Re: list comprehensions

Piers Cawley wrote: Jonathan Scott Duff <[EMAIL PROTECTED]> writes: Will there be some shorter-hand way to say these? @a = @grades[grep $_ >= 90, @grades]; @b = @grades[grep 80 <= $_ < 90, @grades]; @c = @grades[grep 70 <= $_ < 80, @grades]; Granted, it's fairly compact as it is but I'm wo

Re: Supercomma! (was Re: UTF-8 and Unicode FAQ, demos)

On Mon, Nov 04, 2002 at 07:27:56PM -0800, Brian Ingerson wrote: : Mutt? : : I'm using mutt and I still haven't had the privledge of correctly viewing one : of these unicode characters yet. I'm gonna be really mad if you say you're : also using an OS X terminal. I suspect that it's my horrific OS X

Re: perl6-lang Project Management

On Tuesday, November 5, 2002, at 11:18 PM, Allison Randal wrote: Since you're interested in the management of the Perl 6 project, I'll let you in on some of it. Let's start with a step back into a bit of history: OK, let me pause for a second... pause, pause, pause... OK, I'm better now. Pl

Re: list comprehensions

--- Buddha Buck <[EMAIL PROTECTED]> wrote: > I think that if there were a slice-based form of grep, it would most > likely look like you are indexing by a subroutine (or method) > reference > that takes no arguments other than an element of the array. > Something like: > >@a = @grades[{$^x

Re: Supercomma! (was Re: UTF-8 and Unicode FAQ, demos)

On Tue, Nov 05, 2002 at 11:36:45AM -0500, Ken Fox wrote: : Jonathan Scott Duff wrote: : : >Um ... could we have a zip functor as well? I think the common case : >will be to pull N elements from each list rather than N from one, M : >from another, etc. So, in the spirit of timtowtdi: : > : >

Re: perl6-lang Project Management

[EMAIL PROTECTED] (Michael Lazzaro) writes: > Big, Big HOLE in the middle. _Who_ is fleshing out the mindless, > trivial details that Larry posts to this list, and _who_ is > creating/updating the documentation to reflect those changes? Anyone? Allison is, but she was too modest to say so. (And

Re: Perl6 Operator List (REMAINING ISSUES)

[Apologies for late reply, but it takes a long time to read this many messages] On Wed, 30 Oct 2002 16:37:09 -0800, Michael Lazzaro wrote: 1) Need a definitive syntax for hypers, > ^[op] and «op» > have been most seriously proposed -- something that > keeps a bracketed syntax, but

Re: [RFC] Perl Operator List, TAKE 6

On Tue, Nov 05, 2002 at 08:18:18PM +0100, Dennis Haney wrote: : Michael Lazzaro wrote: : : > ~ - force to string context : : > ~ ~= - string concat : : ARG. When did this get chosen? : ~ has to be absolutly the most difficult letter to type on the intire : keyboar

Re: [RFC] Perl Operator List, TAKE 6

On Wed, 6 Nov 2002 11:13:36 -0800 Larry Wall <[EMAIL PROTECTED]> wrote: > You're not supposed to use string concatenation > all that often anyway... I'm not supposed (for some value of supposed) to use Perl at my job, but I do, and I suspect I use string concatenation in about one script in five,

Re: list comprehensions

> Will there be some shorter-hand way to say these? > [list comprehensions] (bb clarified that this is about hash slicing.) >From A2: RFC 201: Hash Slicing ...Concise list comprehensions will require some other syntax within the subscript... And There are many ways we could re

Re: perl6-lang Project Management

On Tue, Nov 05, 2002 at 04:26:58PM -0800, Michael Lazzaro wrote: > So what say you? Can we migrate perl6-language into a list that > finalizes aspects of the design, documents them, and revises them as > needed, rather than our usual circular discussions of things already > long-since past? Wh

Re: list comprehensions

You know, guys, I already discussed this one in A4 or thereabouts. It's the use of an explicit boolean operator as a subscript that triggers selection. Larry

Re: perl6-lang Project Management

On Tue, 05 Nov 2002 23:18:01 -0800, Allison Randal wrote: > If you really want to be involved where the rubber meets the road -- where the > "abstract" design gets tested and every last detail must be fleshed out -- you > might contribute to Parrot. It has a good many of the features of the first

Re: list comprehensions

> I don't see why I'd want to do it with arrays, but... > > %a_students = %grades{grep /^a/i, keys %grades}; Looks like that's just the same as %a_students = grep {.key ~~ :i/^a/}, %grades.kv; (after adjusting for perl6 syntax for a few things) -- Adam Lopresto ([EMAIL PROTECTED]) http://cec.

Re: perl6-lang Project Management

On Wed, Nov 06, 2002 at 06:58:52PM +, Simon Cozens wrote: > [EMAIL PROTECTED] (Michael Lazzaro) writes: > > Big, Big HOLE in the middle. _Who_ is fleshing out the mindless, > > trivial details that Larry posts to this list, and _who_ is > > creating/updating the documentation to reflect those

Re: perl6-lang Project Management

On Wednesday, November 6, 2002, at 10:58 AM, Simon Cozens wrote: It's all at http://cvs.perl.org/cvsweb/perl6/doc/design/ No, that's the Apocalypses and Exegesiii, though very nicely cleaned up. I'm talking about detailed documentation for the things the A's and E's don't cover. MikeL

Re: list comprehensions

On Wed, Nov 06, 2002 at 11:36:50AM -0800, Larry Wall wrote: > You know, guys, I already discussed this one in A4 or thereabouts. > It's the use of an explicit boolean operator as a subscript that > triggers selection. I thought so, but I couldn't find it. thanks, -Scott -- Jonathan Scott Duff [

Re: Perl6 Operator List (REMAINING ISSUES)

Peter Haworth writes: > > @a ^[alpha_op] +3 > > You can parse this in two ways: > * "array a", "hyperop alpha_op", "unary plus", "literal 3" > * "array a", "binary xor", "call alpha_op and put result in arrayref", >"binary plus", "literal 3" > I think this was already discusse d

Re: perl6-lang Project Management

> We started off with an intense RFC process. This produced many good > ideas, not-so-good ideas, and ideas with potential but desperately > needing polish. If you'd like a recap, you might try MJD's article > on the subject (http://www.perl.com/lpt/a/2000/11/perl6rfc.html). > One of the major thin

Re: perl6-lang Project Management

[EMAIL PROTECTED] (Michael Lazzaro) writes: > No, that's the Apocalypses and Exegesiii, though very nicely cleaned > up. I'm talking about detailed documentation for the things the A's > and E's don't cover. Ah, well, they don't cover that. I thought that was what you were doing, right? :) -- S

Re: perl6-lang Project Management

On Wednesday, November 6, 2002, at 12:10 PM, Simon Cozens wrote: [EMAIL PROTECTED] (Michael Lazzaro) writes: No, that's the Apocalypses and Exegesiii, though very nicely cleaned up. I'm talking about detailed documentation for the things the A's and E's don't cover. Ah, well, they don't cov

Re: perl6-lang Project Management

On Wed, Nov 06, 2002 at 01:50:10PM -0600, Allison Randal wrote: > On Wed, Nov 06, 2002 at 06:58:52PM +, Simon Cozens wrote: > > [EMAIL PROTECTED] (Michael Lazzaro) writes: > > > Big, Big HOLE in the middle. _Who_ is fleshing out the mindless, > > > trivial details that Larry posts to this list

Re: perl6-lang Project Management

I'm going to repeat what chromatic said (even though I've deleted his message) On Wed, Nov 06, 2002 at 09:57:58PM +0100, Angel Faus wrote: > - Finish the details that may be not complete in the Apocalypses > (there are plenty of them) write specifications of all the detailed bits as regression t

RE: perl6-lang Project Management

Angel Faus wrote: > > So, while we all wait for Larry to wait the design, is there any > reason not to start working in the documentation? Any chance of getting a wiki setup at: http://dev.perl.org/perl6/cathecism/ Say using a wiki which uses pod for markup like: http://search.cpan.org/auth

RE: perl6-lang Project Management

At 2:26 PM -0600 11/6/02, Garrett Goebel wrote: Angel Faus wrote: So, while we all wait for Larry to wait the design, is there any reason not to start working in the documentation? Any chance of getting a wiki setup at: http://dev.perl.org/perl6/cathecism/ Wikis have serious scaling issu

Re: perl6-lang Project Management

At 9:57 PM +0100 11/6/02, Angel Faus wrote: It's like this: Larry writes the Apocalypses, Damian the Exegesis, and the community writes the Cathecism (a codified, detallied and anonymous explanation of the most boring details of the faith, written in a form that plain people can understand). Mak

Re: perl6-lang Project Management

On Wed, Nov 06, 2002 at 10:54:23AM -0800, Michael Lazzaro wrote: > > -- The "latest news" on the Perl6 section of dev.perl.org was updated > July 7th, introducing Piers, and other than linking to Piers' summaries > contains no information pertinent to Perl6 -- only Parrot. Sounds like a place y

Re: perl6-lang Project Management

On Wednesday, November 6, 2002, at 12:26 PM, Garrett Goebel wrote: Angel Faus wrote: So, while we all wait for Larry to wait the design, is there any reason not to start working in the documentation? Yes! Someone gets it! The Apocalypses and Exegesis are not "formal" documentation, they're

Re: perl6-lang Project Management

At 2:44 PM -0600 11/6/02, Allison Randal wrote: The obstruction you're imagining doesn't exist. The "Parroteers" ask for guidance from Dan. When Dan feels the details aren't clear enough yet he brings the issue to the rest of the design team. When none of us can give him an immediate answer (becau

Re: Draft sketch of bytecode generation

At 11:51 PM +0530 11/6/02, Gopal V wrote: If memory serves me right, Dan Sugalski wrote: (Parrot bytecode is inherently unverifiable as well, at least in the general case, which exacerbates the problem) Hmm... Why ? ... Loose typing ? Or does it just become an undecidability problem ?...

Re: [perl #18219] on_exit not portable

At 9:19 PM +0100 11/6/02, Leopold Toetsch wrote: Summary of changes I did put in WRT this: - interpreter startup code is reordered so that all PMCs/Buffers are in managed memory now. - Long running programs using e.g. new interpreters on the fly would currently leak tons of memory. - Debugging m

Re: Should memory be washed?

At 8:58 PM +0100 11/6/02, Leopold Toetsch wrote: Dan Sugalski wrote: I don't have a problem with guaranteeing zeroed memory, but it's not free. If we're going with a malloc-style allocator then I explicitly do *not* want to give guarantees of zeroed memory. It doesn't make much sense to give

Re: [FYI] life generations

Dan Sugalski wrote: At 12:52 PM +0100 11/6/02, Leopold Toetsch wrote: Here some numbers for examples/assembly/life.pasm (generations/sec) on ... I'm certainly up for arguments that it should be on by default, or with a switch in configure when we want to go run speed demos... No need cur

Re: [CVS ci] string_set is back for a faster live - not only

Dan Sugalski wrote: Substr should generate a new string and stick that into S0. If we want to build a fast version that reuses a string register, I'm fine with that--it's definitely useful in a large number of circumstances, large enough to warrant expressing both sets of semantics. Fine. Bu

Re: [perl #18219] on_exit not portable

Dan Sugalski wrote: - I implemented Parrot_destroy, which cleans up all internal data structures of an interpreter and frees all used mem. Right, I understand. (And I really appreciate it--this was a hanging area that didn't get nearly the proper attention it needed) The bit I don't underst

Re: perl6-lang Project Management

My apologies for one more post, but I find the assertions various people have posted on this topic to be absolutely astounding. On Wednesday, November 6, 2002, at 12:44 PM, Allison Randal wrote: I don't *WANT* to write damn documentation. I wrote a first-chapter summary of some basic Apocalypse

String -> Numeric conversion

If anyone knows the answer to these two questions, I'd appreciate it. 1) What do these do? my int $n = 5; # OK my int $n = 5.005; # trunc or err? my int $n = "5.05ff" # 5, 0, undef, NaN, or exception? my int $n = "fdsjfdf"# 0, undef, NaN, or exception? 2) Do

Re: perl6-lang Project Management

Nicholas Clark wrote: > > Not good. 5 patches means that 4 people wasted effort trying to help. > I don't have a solution to this problem (sorry). But I think it's an > important problem to solve. Wasted effort is a problem. I don't know that a perfect solution exists. Parrot's solution of making

Re: String -> Numeric conversion

> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm > Date: Wed, 6 Nov 2002 14:53:37 -0800 > From: Michael Lazzaro <[EMAIL PROTECTED]> > X-SMTPD: qpsmtpd/0.12, http://develooper.com/code/qpsmtpd/ > > > If anyone knows the answer to these two questions, I'd appreciate it. > > 1) What do these

Re: perl6-lang Project Management

This is getting silly. [EMAIL PROTECTED] (Michael Lazzaro) writes: > Seriously, don't patronize me: it won't get you anywhere productive, > and it just ticks me off. I am not _unaware_ of the current Perl6 > dynamics and management decisions; on the contrary, I am observing > that the current ap

Re: perl6-lang Project Management

At 11:15 PM + 11/6/02, Simon Cozens wrote: I think you're equating a pool of "available" talent and labor with a pool of willing talent and labour. Everyone is willing to offer suggestions, but few people - you being one of the few - are willing to put the time into thrashing these suggestions

Re: perl6-lang Project Management

[EMAIL PROTECTED] (Dan Sugalski) writes: > 1) There *must* be someone who will drive the discussion, or it will > wander off into some bizarre corner and die That's the job of the Apo pumpkin. > 2) Under no circumstances can Larry be allowed to subscribe, or even > read, the lists. :) I thought

Re: perl6-lang Project Management

On Wednesday, November 6, 2002, at 03:34 PM, Dan Sugalski wrote: At 11:15 PM + 11/6/02, Simon Cozens wrote: Here is my suggested solution to the problem. And, though, snipped, a fine solution it is, with two caveats: 1) There *must* be someone who will drive the discussion, or it will

Re: perl6-lang Project Management

At 11:39 PM + 11/6/02, Simon Cozens wrote: [EMAIL PROTECTED] (Dan Sugalski) writes: > 2) Under no circumstances can Larry be allowed to subscribe, or even read, the lists. :) I thought that was so obvious it wasn't worth mentioning. :) It's the blatantly obvious stuff that gets missed t

Re: list comprehensions

"Adam D. Lopresto" <[EMAIL PROTECTED]> writes: >> I don't see why I'd want to do it with arrays, but... >> >> %a_students = %grades{grep /^a/i, keys %grades}; > > Looks like that's just the same as > > %a_students = grep {.key ~~ :i/^a/}, %grades.kv; I think you could probably get away without

Re: String -> Numeric conversion

Luke Palmer <[EMAIL PROTECTED]> writes: >> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm >> Date: Wed, 6 Nov 2002 14:53:37 -0800 >> From: Michael Lazzaro <[EMAIL PROTECTED]> >> X-SMTPD: qpsmtpd/0.12, http://develooper.com/code/qpsmtpd/ >> >> >> If anyone knows the answer to these two que

Re: [perl #18219] on_exit not portable

At 15:57 on 11/06/2002 EST, Dan Sugalski <[EMAIL PROTECTED]> wrote: > >This is was I did say above, just put comments around above > >statement if tinderboxen are the concern. > > Yeah, I think I'll do that for right now. What I'd like is a probe > for this in configure. Oh, Brent :) If an

Primitive Vs Object types

Every primitive type has an associated object type, whose name differs only by capitalized first letter. A few posts back, Larry mentioned that perhaps similar things should look different: this may be a good case to apply this principle. Whenever a value passes through a primitive type, it loses

Re: Primitive Vs Object types

At 6:50 PM -0800 11/6/02, David Whipp wrote: Whenever a value passes through a primitive type, it loses all its run-time properties; and superpositions will collapse. What makes you think so, and are you really sure? -- Dan ---

RE: Primitive Vs Object types

Dan Sugalski [mailto:dan@;sidhe.org] wrote: > At 6:50 PM -0800 11/6/02, David Whipp wrote: > > Whenever a value passes through a primitive type, it > > loses all its run-time properties; and superpositions > > will collapse. > > What makes you think so, and are you really sure? I was sure up unti

RE: Primitive Vs Object types

At 8:24 PM -0800 11/6/02, David Whipp wrote: If I am wrong, then I am in need of enlightenment. What is the difference between the primitive types and their heavyweight partners? And which should I use in a typical script? The big difference is there's no way you can ever truly get a primitive

Re: Primitive Vs Object types

David Whipp wrote: > > Dan Sugalski [mailto:dan@;sidhe.org] wrote: > > At 6:50 PM -0800 11/6/02, David Whipp wrote: > > > Whenever a value passes through a primitive type, it > > > loses all its run-time properties; and superpositions > > > will collapse. > > > > What makes you think so, and are y

RE: Primitive Vs Object types

Dan Sugalski [mailto:dan@;sidhe.org] wrote: > At 8:24 PM -0800 11/6/02, David Whipp wrote: > >If I am wrong, then I am in need of enlightenment. What > >is the difference between the primitive types and their > >heavyweight partners? And which should I use in a typical > >script? > > The big diff

Re: Primitive Vs Object types

I gotta admit that this issue is bugging me too. Larry mentions (in ) that all-uppercase is "ugly" and has "boundary conditions". Maybe it would be helpful to know what conditions ar

Re: perl6-lang Project Management

Dan Sugalski wrote: > Simon Cozens wrote: > > >Here is my suggested solution to the problem. > And, though, snipped, a fine solution it is, with two caveats: There's potential here. If we arrange it so Larry can stay focused and the total productivity of the project increases, we'll have a good t

Re: [CVS ci] string_set is back for a faster live - not only

Leopold Toetsch wrote: > Fine. But how do we know, which version we could take. Please read again > Peter's example. It depends on the semantics of Sx register usage all > over the program IMHO. In an attempt to clarify the positions here, let us start with a shorter example: set S0, "zero" se