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: 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

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: 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

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

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