Re: Rationale for a VM + compiler approach instead of an interpreter?

2014-12-07 Thread Tim Bunce
On Sun, Dec 07, 2014 at 07:58:06AM +0530, Mayuresh Kathe wrote: I am training for computer science, and as a rite of passage, my mentor + guide has asked me to write either an interpreter or a compiler for any language of my choice. Would prefer to work on Perl6. Perhaps write either an

[perl #123116] [BUG] Weird error for code parameters with subsignatures in Rakudo

2014-12-07 Thread Carl Mäsak via RT
masak (): I am not 100% sure the `block (Dog -- Bool)` form should work, or is by spec. The `block:(Dog -- Bool)` form comes from S06:1675. TimToady at one point we required a : because of the ambiguity with sublists of parameters, but we already have a whitespace dep with @foo[3,3] vs @foo

Re: Definitions: compiler vs interpreter [was: Rationale for a VM + compiler approach instead of an interpreter?]

2014-12-07 Thread Parrot Raiser
The practical distinction, surely, is that the output of a compiler is usually kept around, to be run one or more times, whereas the an interpreter always works with the original human-readable source. The distinction mattered a lot more when compiling even a trivial program involved at least the

Using C structs containing pointers from NativeCall?

2014-12-07 Thread Steve Mynott
I was trying to wrap GDBM and was having problems with typedef struct { char *dptr; int dsize; } datum; From /usr/include/gdbm.h (on Debianish system) Since I don't seem to able to pass this sort of structure as use v6; use NativeCall; constant LIB = libgdbm; class