Ehlo:
I'm not too sure if this is necessary but it seems logical to get things
into charsets our compilers can handle. Hopefully this is the correct
approach . . . . also this should NULL terminate in the event that the
entire buffer had not yet been filled.
Roman
Index: string.c
On Wed, 17 Apr 2002, Simon Glover wrote:
# This is a buffer overflow; I'm not quite sure what you're trying to do,
# but this certainly doesn't do it.
I see now, I dont know what the hell I was thinking on that part, the
logic was correct to begin with. what about the transcoding though
On Wed, 17 Apr 2002, Simon Glover wrote:
# +cstring[s-buflen + 1] = 0;
good grief
#
#
# This is a buffer overflow; I'm not quite sure what you're trying to do,
# but this certainly doesn't do it.
shouldnt cstring[s-bufused +1] = \0
to keep us from clobbering the last char? or will
why dont we default to null terminating strings of type native?
if native is what we get when LANG=C it only seems natural to do so.
else we are forced to use wrapper functions a that grow and manipulate
string data any time we need to pass it to standard C functions that
wont accept a
Hey guys:
Here is what I have so far of the string_nprintf function. As of now it
only handles C string backslash escape sequences and regular chars
from the format string. My primary concern is whether I am using
BUFFER_immobile_FLAG the correct way to protect myself from GC. I also
dont
# Keep in mind there is the primitive STRING type which is the S* registers,
# and then there is the PMC (PerlString) which uses vtables.
I am refering to the parrots internal strings e.g. S*
the vtable I am refering to is the 'encoding' vtable of functions in
the string struct
Ok now Im paranoid . . . . .
If I set BUFFER_immobile_FLAG during a string_make to allocate a
temporary string that must be manipulated through the body of a function
will the GC leave it alone? if not what must I do? where is this
immune/immortal/gc_cant_touch_me_yet flag?
Roman
On Tue, 9 Apr 2002, Roman Hunt wrote:
# Ok now Im paranoid . . . . .
# will the GC leave it alone? if not what must I do? where is this
# immune/immortal/gc_cant_touch_me_yet flag?
disregard my last message I now realize that gc wont stop at my STRING's
as I must maintain temporary INTVAL's
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 stdarg.h
--Roman
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()
10 matches
Mail list logo
