sha1 in imcc

you can grab a copy here: http://code.iamcal.com/parrot/sha1.imc works on a few tested 32 bit platforms. fails on 64 bits, due to what looks like a bug with constants and/or sprintf (the low words of the final ints are correct, but trying to clear the high words causes wierdness - thomason is

Re: How can I get involved in the Phalanx Project

stevan little wrote: I looked on the site (http://qa.perl.org/phalanx/), but there was nothing said about how to get involved in this project. Are you looking for help? And if so, how can I help? Thanks, Steve sure. Pick a module from phalanx 100, based upon your personal uses, or whichever mod

RE: is rw trait's effect on signature

On Thu, 2004-05-06 at 13:47, Austin Hastings wrote: > Then in your example: > The class 'Eh' "does A but does not inherit", did you mean: > > class Eh { > method A1 > method A2 > method A3 > } Yes. > I had thought that C (class implicitly= role) had been > rejected. I don't remember in p

How can I get involved in the Phalanx Project

I looked on the site (http://qa.perl.org/phalanx/), but there was nothing said about how to get involved in this project. Are you looking for help? And if so, how can I help? Thanks, Steve

RE: is rw trait's effect on signature

> -Original Message- > From: chromatic [mailto:[EMAIL PROTECTED] > Sent: Thursday, 06 May, 2004 04:36 PM > To: Austin Hastings > Cc: Perl6 Language List > Subject: RE: is rw trait's effect on signature > > > On Thu, 2004-05-06 at 13:27, Austin Hastings wrote: > > > I think we had this dis

RE: is rw trait's effect on signature

On Thu, 2004-05-06 at 13:27, Austin Hastings wrote: > I think we had this discussion a year or two ago, and Damian was opposed to > the notion that providing the correct methods was equivalent to providing > the interface or belonging to the class. > > His reasoning involved Dog and Tree both sha

RE: is rw trait's effect on signature

> -Original Message- > From: chromatic [mailto:[EMAIL PROTECTED] > > Given: > > - class A, a superclass > - class AB, a subclass of A > - class Eh, a class that does A but does not inherit > from it > - subroutine signature foo(A some_object) > > If the sign

Code snippets for the perl 6 compiler

Since it looks like Larry's pretty much done with the meat of perl 6, it's time to start in on getting the compiler written. I'll go nudge Ask again to split the list up so the folks who don't care about Parrot and the folks that don't care about perl can do their respective work in peace. I t

Re: Named parameters vs. slurpy hash syntax: brittle call syntax!

Dov Wasserman wrote: My concern is that given an argument supplied as a pair (foo => "bar"), it is not clear which type of parameter is meant to be supplied. If there is no such named parameter, we know that the argument was intended for the slurpy hash. However, what if the method designer later a

Re: is rw trait's effect on signature

At 11:42 AM -0700 5/6/04, chromatic wrote: On Thu, 2004-05-06 at 11:24, Dan Sugalski wrote: Well... sort of, but only because you've defined that for perl 6 classes automatically do themselves--you've conflated inheritance and interface. Which is fine, except that it falls down in the face of o

Isolated ARENA_DOD_FLAGS problem on Cygwin

Since I am unable to help with the C part of things, I figured I could at least track down where the problem was for everyone. I have isolated the ARENA_DOD_FLAGS problem on Cygwin to a change committed to CVS between 2004-04-15 10:00 and 10:15 EDT. After 10:15, I need to disable it for it to com

Re: Named parameters vs. slurpy hash syntax: brittle call syntax!

"Aldo Calpini" <[EMAIL PROTECTED] > wrote in message ... > > if you decide to reimplement logError to be just: > sub logError {# implicit ([EMAIL PROTECTED]) > # ... > } > using a Pair, you still have someting (a Pair object) that you ca

Re: is rw trait's effect on signature

On Thu, 2004-05-06 at 11:24, Dan Sugalski wrote: > Well... sort of, but only because you've defined that for perl 6 > classes automatically do themselves--you've conflated inheritance and > interface. Which is fine, except that it falls down in the face of > objects from classes that don't do t

Re: is rw trait's effect on signature

At 11:03 AM -0700 5/6/04, Larry Wall wrote: On Thu, May 06, 2004 at 01:52:45PM -0400, Dan Sugalski wrote: : At 10:44 AM -0700 5/6/04, chromatic wrote: : >On Thu, 2004-05-06 at 10:39, Aaron Sherman wrote: : > : >> The simple case is: : >> : >> sub foo(X $i is rw) {...} : >> class X {...} :

Re: is rw trait's effect on signature

On Thu, May 06, 2004 at 01:52:45PM -0400, Dan Sugalski wrote: : At 10:44 AM -0700 5/6/04, chromatic wrote: : >On Thu, 2004-05-06 at 10:39, Aaron Sherman wrote: : > : >> The simple case is: : >> : >>sub foo(X $i is rw) {...} : >>class X {...} : >>class Y {...} : >>my Y $var = 'someth

Re: [perl #29257] Build libnci.so by default

> -Original Message- > From: Leopold Toetsch [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 04, 2004 5:55 AM > To: [EMAIL PROTECTED] > Subject: Re: [perl #29257] Build libnci.so by default > > > Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote: > > > 'libnci.so' is used for testing the na

Re: is rw trait's effect on signature

At 10:44 AM -0700 5/6/04, chromatic wrote: On Thu, 2004-05-06 at 10:39, Aaron Sherman wrote: The simple case is: sub foo(X $i is rw) {...} class X {...} class Y {...} my Y $var = 'something'; foo($var); In this case, something kind of interesting has to hap

Re: Returning from Rules

On Mon, Apr 19, 2004 at 01:06:29AM -0600, Luke Palmer wrote: : Therefore, the first syntax can be redefined to evaluate the code block : and assign the result to $0. The example now becomes: : : rule list { : , <{ make_node('list', $?term, $?list) }> : | <{ $?term

Re: is rw trait's effect on signature

On Thu, 2004-05-06 at 10:39, Aaron Sherman wrote: > The simple case is: > > sub foo(X $i is rw) {...} > class X {...} > class Y {...} > my Y $var = 'something'; > foo($var); > > In this case, something kind of interesting has to happen. > > Either the signature che

Re: is rw trait's effect on signature

At 1:39 PM -0400 5/6/04, Aaron Sherman wrote: There's a subtle problem / feature resulting from the "is rw" trait that may be so obvious that I'm making a fool of myself, or it might be that it's not yet occurred, but I don't recall seeing discussion of it. The simple case is: sub foo(X $i

is rw trait's effect on signature

There's a subtle problem / feature resulting from the "is rw" trait that may be so obvious that I'm making a fool of myself, or it might be that it's not yet occurred, but I don't recall seeing discussion of it. The simple case is: sub foo(X $i is rw) {...} class X {...} c

Re: Named parameters vs. slurpy hash syntax: brittle call syntax!

On Wed, 2004-05-05 at 22:36, Dov Wasserman wrote: > sub logError($msg, Int +$prio = 4, *%errorInfo) { [...] > logError("Database error", module => "DB.pm", line => 263, prio => "HIGH"); > > After the New And Improved logError() routine is rolled out, it seems to me > that this log statement shoul

Re: [perl #29257] Build libnci.so by default

On Thu, May 06, 2004 at 06:21:23PM +0200, Leopold Toetsch wrote: > Nicholas Clark wrote: > > 0 loadlib P1, "libnci" - P1=NULL, > > 3 dlfunc P0, P1, "nci_pi", "pi"- P0=NULL, > > P1=ParrotLibrary=PMC(0x200f7f0), , DOD > > 8 set I5, 5- I5=0, > > That seems to be nci

Re: [CVS ci] NCI sub call syntax in PIR

At 9:12 AM +0200 5/6/04, Leopold Toetsch wrote: A bit less typing for NCI calls: 1) declare the pmc type as NCI .local NCI the_sub # get it from somewhere e.g.: # the_sub = global "ncurses::initscr" 2) just call it: r = the_sub(args) Works only for named subs of course. This saves a save

Re: [perl #29257] Build libnci.so by default

Nicholas Clark wrote: 0 loadlib P1, "libnci" - P1=NULL, 3 dlfunc P0, P1, "nci_pi", "pi"- P0=NULL, P1=ParrotLibrary=PMC(0x200f7f0), , DOD 8 set I5, 5- I5=0, That seems to be nci_23 from CVS, which is weird: that looks totally different here. This test uses a

Parrot test results on Cygwin

FYI: Extend test #12 was disabled because it was hanging on Cygwin and you had to kill the process in another window for the test suite to complete. This is now happening on #13 as well. Failed Test Stat Wstat Total Fail Failed List of Failed --

Re: [perl #29257] Build libnci.so by default

On Thu, 6 May 2004, Leopold Toetsch wrote: > Nicholas Clark <[EMAIL PROTECTED]> wrote: > > On Fri, Apr 30, 2004 at 01:14:21PM +0200, Leopold Toetsch wrote: > > >> Good. Do we have currently any platforms that don't support dynamic > >> loading at all? > > > Perl5 builds on UNICOS (Crays), which is

Re: Cygwin problems are GC not ICU

--- Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Somethings is *really* wrong here. I don't know > exactly what's happening > here, but I assume that the memalign function is > buggy. To nail that > further down: > > 1) Determine the used memalign function: > > $ grep memalign lib/Parrot/Config.p

Cygwin works - lessons learned

All, It is still unclear to me if turning off ARENA_DOD_FLAGS in include/parrot/pobj.h is required yet or not. Leo suspects a broken memalign function but since parrot was working prior to April 7th and nothing changed except parrot, I am not too sure. As soon as this posts I will start digging a

Re: [perl #29257] Build libnci.so by default

On Thu, May 06, 2004 at 04:43:53PM +0200, Leopold Toetsch wrote: > Nicholas Clark <[EMAIL PROTECTED]> wrote: > > > +$(LIBNCI_SO): $(SRC)/nci_test$(O) > > $(LD) $(LD_SHARED) $(LDFLAGS) \ > > $(LD_OUT)$@ $(SRC)/nci_test$(O) > > Win32 additionally needs the libnci.def thingy. (Except whe

Re: Named parameters vs. slurpy hash syntax: brittle call syntax!

On Thu, 2004-05-06 at 02:36, Dov Wasserman wrote: > To distinguish these two cases, what if we used the := binding operator to > bind an argument to a named parameter: > > logError($err_msg, prio := 3); but how would this look like to a subroutine that is not defined to accept a named parameter c

Re: [perl #29385] [PROPOSED PATCH] Return Nested Structs from Structs

Chromatic <[EMAIL PROTECTED]> wrote: > The attached patch allows you to fetch nested structs from their > enclosing structs. Hehe, where's that "I'm not a C programer"? Great. > - it reuses the PMC from the struct initializer, so there's a > possibility of yanking the rug out from someone

Re: [perl #29257] Build libnci.so by default

Nicholas Clark <[EMAIL PROTECTED]> wrote: > +$(LIBNCI_SO): $(SRC)/nci_test$(O) > $(LD) $(LD_SHARED) $(LDFLAGS) \ > $(LD_OUT)$@ $(SRC)/nci_test$(O) Win32 additionally needs the libnci.def thingy. (Except when we put in the proposed dll_export macros). > (gdb) print *obj > $1 = { >

Re: [perl #29257] Build libnci.so by default

On Tue, May 04, 2004 at 02:55:25PM +0200, Leopold Toetsch wrote: > Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote: > > > 'libnci.so' is used for testing the native call interface. However I noticed > > that the tests in t/pmc/nci.t were skipped, because 'libnci.so' wasn't built > > by default. The

Re: Named parameters vs. slurpy hash syntax: brittle call syntax!

"Aldo Calpini" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > On Thu, 2004-05-06 at 02:36, Dov Wasserman wrote: > > > > After the New And Improved logError() routine is rolled out, it seems to me > > that this log statement should generate a compile-time error, since the > > named In

Re: Named parameters vs. slurpy hash syntax: brittle call syntax!

On Thu, 2004-05-06 at 02:36, Dov Wasserman wrote: > After the New And Improved logError() routine is rolled out, it seems to me > that this log statement should generate a compile-time error, since the > named Int parameter "prio" is given a non-integer argument "HIGH". At best, > this should be a

Re: Cygwin problems are GC not ICU

Joshua Gatcomb <[EMAIL PROTECTED]> wrote: > --- Leopold Toetsch <[EMAIL PROTECTED]> wrote: >> (gdb) bt >> (gdb) p pmc >> /gdb) p *((Dead_PObj*)pmc) >> would be good. > Program received signal SIGSEGV, Segmentation fault. > #5 0x0053fb75 in Parrot_ParrotInterpreter_class_init Early in program st

Re: parrot once again working on Cygwin

Joshua Gatcomb <[EMAIL PROTECTED]> wrote: > --- Leopold Toetsch <[EMAIL PROTECTED]> wrote: >> turn off >> ARENA_DOD_FLAGS in include/parrot/pobj.h line 25. > Is this a work-around or the actual fix? More the former. > because I plan on drafting up some notes on the > various ways to get ICU work

Re: [perl #29257] Build libnci.so by default

Nicholas Clark <[EMAIL PROTECTED]> wrote: > On Fri, Apr 30, 2004 at 01:14:21PM +0200, Leopold Toetsch wrote: >> Good. Do we have currently any platforms that don't support dynamic >> loading at all? > Perl5 builds on UNICOS (Crays), which is a Unix without dynamic linking. > (As my housemate expl

Re: [perl #29380] [Test PATCH] Accessing Pointers in Structs as Aggregates

Chromatic <[EMAIL PROTECTED]> wrote: > typedef struct SDL_Surface { > void *pixels; /* Read-write */ > ... > } > I'd like to be able to access pixels (an array of Uint32s) directly in > some cases. > + set P2[ 'i' ], .DATATYPE_PTR Why not

[CVS ci] NCI sub call syntax in PIR

A bit less typing for NCI calls: 1) declare the pmc type as NCI .local NCI the_sub # get it from somewhere e.g.: # the_sub = global "ncurses::initscr" 2) just call it: r = the_sub(args) Works only for named subs of course. This saves a savetop/restoretop pair and creating a return contin

Re: A12: Required Named Parameters Strike Back!

"Larry Wall" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > On Wed, May 05, 2004 at 04:25:45PM -0400, Austin Hastings wrote: > : > : method x ($me: $req, ?$opt, +$namedopt, *%named, [EMAIL PROTECTED]) {...} > : vs: > : method x($me: $req, ?$opt, ~$namedopt, *%named, [EMA

Named parameters vs. slurpy hash syntax: brittle call syntax!

[Reposting this from earlier this week, since it didn't seem to make it to the news server. -dmw] A question about the calling syntax of named parameters versus arguments supplied to a slurpy hash. If I understand A6 and A12 correctly, all Pair arguments to a function (sub, method, etc.) are scann