At 01:48 AM 4/9/2002 -0400, Michel J Lambert wrote:
> > the malloc()/free() situation which is one of the primary reasons we
> > use garbage collection in the first place, so why reinvent the same
> > situation with different syntax?
>
>Generally, malloc/free are used in more complex situations th
> I agree we need an overall architectural solution. Setting and clearing
> bits manually is error-prone but fast, as you said. Its identical to
> the malloc()/free() situation which is one of the primary reasons we
> use garbage collection in the first place, so why reinvent the same
> situation
At 01:17 AM 4/9/2002 -0400, Michel J Lambert wrote:
The first example is the following code, which calls parrot_allocate to
>create the string each time.
Might both of these be solved by using arenas?
-Melvin
At 10:30 PM 4/8/2002 -0700, Robert Spier wrote:
>>Keep track of global (or interpreter local) scope with a macro
>>upon entry.
>
>I shudder every time someone says "macro" on p6i.
>
>perl5 has several thousand macros defined. (grep for ^#define) (over 8000
>if you include all the embedding macr
> Keep track of global (or interpreter local) scope with a macro
> upon entry.
I shudder every time someone says "macro" on p6i.
perl5 has several thousand macros defined. (grep for ^#define) (over
8000 if you include all the embedding macros. it's down to ~4000 if you
cut out embedding, co
I think I know of two potential performance problems with the GC code.
They could be problems in my head, or real problems, as I haven't done any
profiling. We also don't have any real test cases. :)
The first example is the following code, which calls parrot_allocate to
create the string each
At 11:40 PM 4/8/2002 -0400, Michel J Lambert wrote:
> > 2) I'm thinking of an internal stack not visible to user code that we use
> > for temporary PMCs and Buffers and a simple macro for entry and
> > exit of GC sensitive routines. I think I might have mentioned this.
>
>What defines a
On Mon, Apr 08, 2002 at 11:40:28PM -0400, Michel J Lambert wrote:
> However, if we can't find all the places we do buffer manipulation to mark
> them immortal, how are we going to properly identify all the GC-sensitive
> functions?
Ack! Sorry for being anal, but I finally decided the 'immortal' n
> >This message does remind me of how empty the TODO list is. Surely we
> >can think of many more things to be done?
>
> Speaking of..
>
> 1) Bugfix release please, we banged quite a few stack and GC bugs out.
> Don't we get any dessert?
Peter has already stated he'd like his parrot_realloca
# New Ticket Created by "Clinton A. Pierce"
# Please include the string: [netlabs #500]
# in the subject line of all future correspondence about this issue.
# http://bugs6.perl.org/rt2/Ticket/Display.html?id=500 >
Compiling BASIC into out.pbc:
C:\projects\parrot\parrot>basic.pl [produces o
At 06:10 PM 4/8/2002 -0700, Steve Fink wrote:
>On Mon, Apr 08, 2002 at 07:01:44PM -0400, Melvin Smith wrote:
> > At 05:49 PM 4/8/2002 -0400, Roman Hunt wrote:
> > >find the definition for the string_vtable it is not in
> >
> > Try classes/perlstring.pmc
> >
> > Keep in mind there is the pr
On Mon, Apr 08, 2002 at 07:01:44PM -0400, Melvin Smith wrote:
> At 05:49 PM 4/8/2002 -0400, Roman Hunt wrote:
> >find the definition for the string_vtable it is not in
>
> Try classes/perlstring.pmc
>
> Keep in mind there is the primitive STRING type which is the S* registers,
> and then
At 05:49 PM 4/8/2002 -0400, Roman Hunt wrote:
>hello:
> and importance, but I feel up to the task. (Read: "Please, be
> patient with the newbie"). I have begun work on
The more the merrier, its been too quiet this last week.
> find the definition for the string_vtable i
hello:
I am interested in contributing to the project. (Thank Dan's
cross-country tour :) This is my first project of this size
and importance, but I feel up to the task. (Read: "Please, be
patient with the newbie"). I have begun work on
string_nprintf()
Melvin Smith <[EMAIL PROTECTED]> writes:
> I would expect that should be fine, stdarg is one of the 4 headers that
> are guaranteed by ANSI C89 even on a free standing environment (read
> embedded targets, etc.)
> Its integral to C, and if you don't have it, I suppose the question
> would be why
At 6:32 PM -0400 4/7/02, Roman Hunt wrote:
>Hello all:
> I was just begining work on the string api and was wondering what
> libraries are allowed for use inside the interpreter. Mainly
> I want to know if I can use
As Melvin's said, that's fine. Pretty much everything else needs a
Confi
At 06:32 PM 4/7/2002 -0400, Roman Hunt wrote:
>Hello all:
> I was just begining work on the string api and was wondering what
> libraries are allowed for use inside the interpreter. Mainly
> I want to know if I can use
I would expect that should be fine, stdarg is one of the 4 headers
tha
Hello all:
I was just begining work on the string api and was wondering what
libraries are allowed for use inside the interpreter. Mainly
I want to know if I can use
--Roman
18 matches
Mail list logo
