Re: String API

2003-08-20 Thread Leopold Toetsch
Benjamin Goldberg wrote: Leopold Toetsch wrote: Not having an INTERP argument severely limits us, even in other ways. The INTERP argument is fine. The user defined encoding is/was my problem. Similarly, that would eliminate the chance of a STRING* which is actually a lazily concatenated list of

Activity on mod_parrot?

2003-08-20 Thread Tim Fries
Greetings, Has there been any active development on mod_parrot since last year? The CVS on perl.org seems to have lost steam on the project 11 months ago. This is an area I'm interested in tinkering around with a bit to get to learn Parrot better and possibly be useful at the same time, but I

Re: Timely Destruction: An efficient, complete solution

2003-08-20 Thread Benjamin Goldberg
Dave Mitchell wrote: > > On Wed, Aug 20, 2003 at 06:40:51PM -0400, Benjamin Goldberg wrote: > > Dave Mitchell wrote: > > > > > > On Sun, Aug 17, 2003 at 05:48:14AM -0600, Luke Palmer wrote: > > > > Here comes that ever-reincarnating thread again, sorry. > > > > > > > > This is a proposal for an ef

RE: [RfC] constant PMCs and classes

2003-08-20 Thread Brent Dax
Leopold Toetsch: # The property 'constant', 'ro' or whatever can only be some kind of # communication: the HLL is telling the PMC to be read only. We could now # have in each set-like vtable: # #if (we_have_props && !is_bool(prop("ro")) // pseudo code # set_the_value ... #else #

Re: [RfC] constant PMCs and classes

2003-08-20 Thread Leopold Toetsch
Brent Dax wrote: Leopold Toetsch: # The property 'constant', 'ro' or whatever can only be some kind of # communication: the HLL is telling the PMC to be read only. We could now # have in each set-like vtable: # #if (we_have_props && !is_bool(prop("ro")) // pseudo code # set_the_value ..

Why constant items

2003-08-20 Thread Leopold Toetsch
$ parrot -p lex.pasm # [1] 0.041843 0.810558 ... CODE OP FULL NAMECALLS TOTAL TIMEAVG TIME - - --- -- -- 1138 Exception 10.6977070.70 You for sure can now say, that my exception handling stuff

Re: String API

2003-08-20 Thread Benjamin Goldberg
Leopold Toetsch wrote: > > Benjamin Goldberg <[EMAIL PROTECTED]> wrote: > > Leopold Toetsch wrote: > >> > >> Benjamin Goldberg <[EMAIL PROTECTED]> wrote: > >> > There are a number of shortcomings in the API, which I'd like to > >> > address here, and propose improvments for. > >> > >> > To allow

Re: hash access

2003-08-20 Thread Sean O'Rourke
Leopold Toetsch <[EMAIL PROTECTED]> writes: > We have keyed_int shortcuts to get/set items on array like aggregates. > Is there a reason, that we not have keyed_str to access hash elements > by STRING directly. I'm not so sure this would be worth it; since hash lookups are much more expensive tha

Should I target Parrot?

2003-08-20 Thread Tom Locke
Hi All, I am currently embarking on a project to create a new language. Right now I'm in the process of selecting the platform that's going to give me the best starting point. My first choice is whether to go for a VM, or a C-Python style implementation. Right now I'm leaning towards VM. The lan

Re: Timely Destruction: An efficient, complete solution

2003-08-20 Thread Dave Mitchell
On Wed, Aug 20, 2003 at 06:40:51PM -0400, Benjamin Goldberg wrote: > Dave Mitchell wrote: > > > > On Sun, Aug 17, 2003 at 05:48:14AM -0600, Luke Palmer wrote: > > > Here comes that ever-reincarnating thread again, sorry. > > > > > > This is a proposal for an efficient solution to the timely destru

Re: Timely Destruction: An efficient, complete solution

2003-08-20 Thread Benjamin Goldberg
Dave Mitchell wrote: > > On Sun, Aug 17, 2003 at 05:48:14AM -0600, Luke Palmer wrote: > > Here comes that ever-reincarnating thread again, sorry. > > > > This is a proposal for an efficient solution to the timely destruction > > problem, which doesn't use refcounting, and fits in to the current

hash access

2003-08-20 Thread Leopold Toetsch
We have keyed_int shortcuts to get/set items on array like aggregates. Is there a reason, that we not have keyed_str to access hash elements by STRING directly. Currently a hash access inside parrot needs a key_new_string() which contructs a new Key PMC, where the string then gets extracted again

Re: [RfC] constant PMCs and classes

2003-08-20 Thread Leopold Toetsch
Brent Dax wrote: Leopold Toetsch: # Further we would need for some classes a Const$Class variant, where the # set-like vtables throw an exception. These classes should be # autogenerated from *.pmc for all classes that have a "const_too" or such # in their classes $flags. Isn't The Plan(tm) to use

Re: Error in UTF8 encoding (Committed)

2003-08-20 Thread Leopold Toetsch
Peter Gibbs wrote: Leopold Toetsch wrote: [bogus error] Sorry for the false alarm. YAMDI[1] leo [1] Yet Another Missing Dependencies Issue make realclean did help

RE: [RfC] constant PMCs and classes

2003-08-20 Thread Brent Dax
Leopold Toetsch: # Further we would need for some classes a Const$Class variant, where the # set-like vtables throw an exception. These classes should be # autogenerated from *.pmc for all classes that have a "const_too" or such # in their classes $flags. Isn't The Plan(tm) to use properties for t

[RfC] constant PMCs and classes

2003-08-20 Thread Leopold Toetsch
We currently have constant Key and Sub PMCs both created from the packfile at load time. They live in the constant_table pointing to a constant PMC pool. But we need more. We have allover the core code like this: string_from_cstring(interpreter, "pIt", 0) key = key_new_cstring(interpreter,

Re: Error in UTF8 encoding (Committed)

2003-08-20 Thread Leopold Toetsch
Peter Gibbs <[EMAIL PROTECTED]> wrote: > Hi all > I am back to playing with parrot for a while. Fine, welcome back. > Discovered that the UTF8 encoding function was producing > garbage courtesy of two macros in unicode.h; I have fixed > these and added a test to string.t that does a transcode to

[PATCH]Build system

2003-08-20 Thread Vladimir Lipskiy
>We have missing dependencies. E.g. classes/* isn't rebuilt, when some >parrot include files change. This patch deals with only classes/*.pmc dependies. And I have no idea how to search out other missing dependies. headers.pl needs putting into the config/init directory headers.pl Description:

Re: Error in UTF8 encoding (Committed)

2003-08-20 Thread Peter Gibbs
Leopold Toetsch wrote: > Still something fishy: > > $ parrot t/op/string_117.pasm | od -c > 000 A S C I I i s t h e s a m > 020 e a s U T F 8 \n 200 200 200 200 200 200 > 040 200 200 200 200 200 200 200 200 200 200 200 200 20

Error in UTF8 encoding (Committed)

2003-08-20 Thread Peter Gibbs
Hi all I am back to playing with parrot for a while. Discovered that the UTF8 encoding function was producing garbage courtesy of two macros in unicode.h; I have fixed these and added a test to string.t that does a transcode to UTF8. Patch below - but has already been committed, since nobody eve

[perl #23430] [PATCH] Kate syntax highlighter

2003-08-20 Thread via RT
# New Ticket Created by Andy Bussey # Please include the string: [perl #23430] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=23430 > This is a shameless theft of Luke Palmer's cool idea for a generated editor syntax highl

Continuations and COWed stacks (was: search_lex (again)...)

2003-08-20 Thread Leopold Toetsch
Jos Visser <[EMAIL PROTECTED]> wrote: > My current code generator generates code to trap the LEX_NOT_FOUND > exception. However, the "set_eh" instruction is *terribly* slow... After having a closer look at this, I can describe what's happening: - the exception handler is a continuation - these h

Re: search_lex (again)...

2003-08-20 Thread Leopold Toetsch
Jos Visser <[EMAIL PROTECTED]> wrote: > Hi all, > In my case my "problem" (challenge) is that I want to generate some > parrot code that is capable of searching the lexical pads for the > existence of a lexical. In my particular case this code executes > frequently. I would implement the proposed

Re: String API

2003-08-20 Thread Leopold Toetsch
Benjamin Goldberg <[EMAIL PROTECTED]> wrote: > Leopold Toetsch wrote: >> >> Benjamin Goldberg <[EMAIL PROTECTED]> wrote: >> > There are a number of shortcomings in the API, which I'd like to >> > address here, and propose improvments for. >> >> > To allow user-defined encodings, and user-defined tr