"Non-yet-thrown exceptions must be a useful concept."

"Non-yet-thrown exceptions must be a useful concept." This is a bullet point from a list in Apo4 introducing coverage of exception handling. Was Larry talking about an exception object that hasn't yet been thrown? Did he refer to this issue again anywhere else in the Apo? --me

Parrot strings: are strings like "\x{FF10}" false?

Hi, Which Parrot strings are supposed to be false in a boolean context? For instance, is "\x{FF10}" (FULLWIDTH DIGIT ZERO) false? docs/strings.pod says[1] a string is false if it "consists of one digit character whose numeric value (as decided by its character type) is zero". However, string.c

Re: CPP Namespace pollution

On Fri, 25 Jan 2002, Melvin Smith wrote: > >Hm, the FAQ would be not linked from either of dev.perl.org or > >www.parrotcode.org. That's a bummer. > > >Ask, could we move this to dev.perl.org please? > > Dare I suggest we check it into the repository and have a script > update the site from the r

Re: Config police

On Fri, Jan 25, 2002 at 11:14:38PM -0500, Melvin Smith wrote: > Nope, it isn't defined. Why I mentioned it is I was working on > compiling for WindowsCE for an iPAQ and was included > regardless of config. WinCE SDK doesn't have errno.h (I can fake it though) > but I figured it we should have an

Re: Config police

> Bletch. Unless I'm much mistaken that means that WinCE SDK therefore isn't > a full ANSI conformant C library. [Which it is allowed to be - IIRC > compilers without libraries are "allowed"] > I can't remember all the terms for compilers that are conformant but don't > have the libraries but I am

Re: Parrot strings: are strings like "\x{FF10}" false?

On Sat, 26 Jan 2002, David Chan wrote: > Hi, > > Which Parrot strings are supposed to be false in a boolean context? > For instance, is "\x{FF10}" (FULLWIDTH DIGIT ZERO) false? > > docs/strings.pod says[1] a string is false if it "consists of one > digit character whose numeric value (as decided

Re: 123_456

On Fri, 25 Jan 2002 17:34:12 +, Simon Cozens wrote: >Should we be allowed to use _ to group numbers, now that _ is concat? >If not _, then what? (if anything?) I don't really understand your question. Currently, "." is used for concat and that doesn't inhibit using it in a number, does it? O

Re: Parrot strings: are strings like "\x{FF10}" false?

On Sat, Jan 26, 2002 at 10:42:17AM +, David Chan wrote: > Which Parrot strings are supposed to be false in a boolean context? Thinking more deeply about this, I guess it depends entirely on the language, although we can provide string_bool as a sensible default. > For instance, is "\x{FF10}

JIT Regression

I'm sure I wasn't seeing this before: % ./test_parrot -j examples/assembly/mops.pbc Iterations:1zsh: 17990 illegal hardware instruction -- Hildebrant's Principle: If you don't know where you are going, any road will get you there.

GCC-specific (?) options in Makefile.in

Intel's icc doesn't like the -Wl,... What's it doing there, anyway? blib/lib/libparrot$(SO).${VERSION}: $(O_FILES) $(LD) -shared -Wl,-soname,libparrot$(SO).${MAJOR} $(LDFLAGS) -o blib/lib/libparrot$(SO).${VERSION} $(O_FILES) blib/lib/libcore_prederef$(SO).${VERSION}: core_ops_prederef$(O)

Re: Comm. Unity - (was Re: CPP Namespace pollution)

On Friday 25 January 2002 18:55, Simon Cozens wrote: > On Fri, Jan 25, 2002 at 01:56:20PM -0500, Bryan C. Warnock wrote: > > If anything, it's largely our fault, for allowing, through our silence, > > Simon to speak on our behalf in those situations. > > Hey, if my speaking on behalf of Perl 6 is

Re: CPP Namespace pollution

At 4:55 PM -0500 1/25/02, Andy Dougherty wrote: >Sounds like a good plan. Perhaps something like the following patch is in >order then, more as a reminder for the future than anything actually >useful for now? (Note the changed file names: parrot/parrot_e*.h is >apparently redundant and definite

Re: What can be hyperoperated?

> "Larry" == Larry Wall <[EMAIL PROTECTED]> writes: Larry> @result = for @a; @b -> $a, $b { $a op $b } Larry> (presuming we make C actually act like C). Why not just make map do that? -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[EMAIL PROTECTED]> ht

Re: What can be hyperoperated?

> Larry> @result = for @a; @b -> $a, $b { $a op $b } > > Larry> (presuming we make C actually act like C). > > Why not just make map do that? The order of C's arguments is wrong. To make the -> extraction syntax work we need the data being iterated to be on the left and the processor block

Barewords and subscripts

A4 said that there were no barewords in Perl 6. Does this mean that $foo{bar} actually should be written %foo{"bar"} ? I'm vaguely hoping that the answer is yes, because then we could treat *all* instances of {...} as a block returning either a closure, a value for subscripting, or an ano

Re: Barewords and subscripts

At 05:01 PM 1/26/02 +, Simon Cozens wrote: >A4 said that there were no barewords in Perl 6. Does this mean that > $foo{bar} >actually should be written > %foo{"bar"} >? No. That's not a bareword. >I'm vaguely hoping that the answer is yes, because then we could treat >*all* instance

Re: Barewords and subscripts

On Sat, Jan 26, 2002 at 09:28:18AM -0800, Peter Scott wrote: > >%foo{"bar"} It's bare, and it's a word. I presume you're also happy with these ambiguities: $foo{shift} vs. $foo{"shift"} $foo{bar} vs. sub bar() { ... } $foo{bar} vs. $foo{+bar} vs. $foo{b

Re: Apoc4: The loop keyword

In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Jonathan Scott Duff) wrote: > On Fri, Jan 25, 2002 at 11:57:25AM +0100, Bart Lateur wrote: > > On Mon, 21 Jan 2002 15:43:07 -0500, Damian Conway wrote: > > > > >What we're cleaning up is the ickiness of having things declared > > outside > > >t

Warnock's dilemma [PATCH] harness just the tests you want

Any thoughts on this patch? - Forwarded message from Nicholas Clark <[EMAIL PROTECTED]> - Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe:

Re: Apoc4: The loop keyword

On Fri, Jan 25, 2002 at 12:50:51PM -0800, Erik Steven Harrison wrote: > >>Besides no one has commented on Steve Fink's (I think it was him) idea > >>to store the result of the most recently executed conditional in $?. I > >>kinda like that idea myself. It makes mnemonic sense. > > H . . . I c

Re: What can be hyperoperated?

On Fri, Jan 25, 2002 at 06:03:55PM -0800, Larry Wall wrote: > Do they need to? In the simple case, the hyperoperator provides list > context to its arguments, but just calls the scalar operation repeatedly > to fake up the list operation. Any operator > > @result = @a ^op @b > > is really

Re: Barewords and subscripts

At 05:43 PM 1/26/02 +, Simon Cozens wrote: >On Sat, Jan 26, 2002 at 09:28:18AM -0800, Peter Scott wrote: > > >%foo{"bar"} > >It's bare, and it's a word. Maybe you want to come up with another term to describe it then... but it isn't a "bareword" in Perl. Camel III p.64 footnote: "... It

Re: Warnock's dilemma [PATCH] harness just the tests you want

On Sat, Jan 26, 2002 at 05:47:19PM +, Nicholas Clark wrote: > Any thoughts on this patch? It should go in. Sorry. It's in now, thanks. -- Relf Test Passed.

I send too much mail...

And this is one of them. So, for Bryan, who's keeping track... "This is my 2500th message" :) Dan

Re: Barewords and subscripts

>Maybe there will be a Perl 6 rule forcing the keys to be quoted, but it >won't be because of the "no barewords" rule. If there were such a rule, I >presume you'd also apply it to the LHS of =>? There is another way to resolve the ambiguity of foo meaning either "foo" or foo() depending on curre

Parrot test harness and stdout/stderr

Dan, I am gonna turn off -debug in the interp test below, since the test harness is picking up stderr as well as stdout and the test below is failing. (-d causes Parrot to be talkative, no pun intended) It just showed up when I fixed in interpreter local IO stuff (will commit later). Can the te

[MAYBE PATCH] the 2 warnings in jit.c

Appended patch gets rid of these two: cc -pipe -Os -Wall -Wstrict-prototypes -Wmissing-prototypes -Winline -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wconversion -Waggregate-return -Winline -W -Wsign-compare -Wno-unused-I./include -DHAS_JIT -DI386 -o jit.o -c jit.

Re: Parrot test harness and stdout/stderr

On Sat, 26 Jan 2002, Melvin Smith wrote: > Dan, I am gonna turn off -debug in the interp test below, since the > test harness is picking up stderr as well as stdout and the test > below is failing. (-d causes Parrot to be talkative, no pun intended) > > It just showed up when I fixed in interpret

sometimes you just can't win...

cc -pipe -Os -Wall -Wstrict-prototypes -Wmissing-prototypes -Winline -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wconversion -Waggregate-return -Winline -W -Wsign-compare -Wno-unused-I./include -DHAS_JIT -DI386 -o encodings/utf8.o -c encodings/utf8.c encodings/utf8.

Re: sometimes you just can't win...

On Sat, Jan 26, 2002 at 10:17:12PM +, Nicholas Clark wrote: > But I can't see a way to tell gcc that we want to do this and locally > no warnings 'cast-qual'; (if you see what I mean) > There don't seem to be pragmata to do this, and I can't spot an obvious > construction to launder away the c

Re: Parrot test harness and stdout/stderr

At 10:10 PM 1/26/2002 +, Alex Gough wrote: >On Sat, 26 Jan 2002, Melvin Smith wrote: > > > Dan, I am gonna turn off -debug in the interp test below, since the > > test harness is picking up stderr as well as stdout and the test > > below is failing. (-d causes Parrot to be talkative, no pun in

Re: Parrot test harness and stdout/stderr

At 06:01 PM 1/26/2002 -0500, Melvin Smith wrote: >At 10:10 PM 1/26/2002 +, Alex Gough wrote: >>On Sat, 26 Jan 2002, Melvin Smith wrote: >> >> > Dan, I am gonna turn off -debug in the interp test below, since the >> > test harness is picking up stderr as well as stdout and the test >> > below i

Re: [MAYBE PATCH] the 2 warnings in jit.c

It will add a warning per call to calculate_displacement in the alpha. Daniel Grunblatt. On Sat, 26 Jan 2002, Nicholas Clark wrote: > Appended patch gets rid of these two: > > cc -pipe -Os -Wall -Wstrict-prototypes -Wmissing-prototypes -Winline -Wshadow >-Wpointer-arith -Wcast-qual -Wcast-al

Re: What can be hyperoperated?

Damian Conway writes: : > Larry> @result = for @a; @b -> $a, $b { $a op $b } : > : > Larry> (presuming we make C actually act like C). : > : > Why not just make map do that? : : The order of C's arguments is wrong. To make the -> extraction : syntax work we need the data being iterated to b

Re: What can be hyperoperated?

Larry pondered: > Perhaps we shouldn't be using ; for this. That has occurred to me on several occasions but, checking my pockets, I find I'm fresh out of spare symbols to replace it with. We could always use colon, of course ;-) Damian

Re: "Non-yet-thrown exceptions must be a useful concept."

Me writes: : "Non-yet-thrown exceptions must be a useful concept." : : This is a bullet point from a list in Apo4 introducing : coverage of exception handling. Was Larry talking : about an exception object that hasn't yet been thrown? : Did he refer to this issue again anywhere else in the Apo?

Re: What can be hyperoperated?

[EMAIL PROTECTED] writes: : Larry pondered: : : > Perhaps we shouldn't be using ; for this. : : That has occurred to me on several occasions but, checking my pockets, I : find I'm fresh out of spare symbols to replace it with. : : We could always use colon, of course ;-) Well, more likely than

Re: What can be hyperoperated?

On Sat, Jan 26, 2002 at 04:52:53PM -0800, Larry Wall wrote: > @result = map -> $a; $b { $a op $b } @a; @b; Something seems wrong with this, but I can't quite put my finger on what it is. I think it's the -> directly after map - -> looks too much like an operator. And even if you read "->" as

Re: What can be hyperoperated?

Simon wrote: > Given hyperoperators, I wonder if we can actually drop map. So: @result = map { block } @data; becomes: @result = {block}^.(@data); Hmmm. Damian

Re: What can be hyperoperated?

> On the other hand, semicolon works out really nicely within brackets > for multidimensional slices, and the mathematicians like it. And I > don't know how the :: would fit in with other adverbial generalities. Yes, I think semicolon is the correct solution. We just have to explain that it's o

PMCs leaking memory

Hi. I am still writing on my complex number class. When trying to add addition and subtraction methods, I came across the following problem: PMC functions writing results in a destination PMC like add(PMC *dest, PMC *val) overwrite the destination PMC's vtable and cache with new values without t

Re: PMCs leaking memory

On Sat, 26 Jan 2002, Boris Tschirschwitz wrote: > I am still writing on my complex number class. > When trying to add addition and subtraction methods, I came across the > following problem: > > PMC functions writing results in a destination PMC like add(PMC *dest, PMC > *val) overwrite the dest