On Sun, 2002-08-18 at 18:53, Brent Dax wrote:
> # And do we need a RFC like definition of should/may/must/mustn't?
>
> If so, I'd suggest the definition be patched into PDD0, so it's shared
> by all PDDs instead of repeating the definitions everywhere.
Noted.
--
Bryan C. Warnock
bwarnock@(gtem
"Brent Dax" <[EMAIL PROTECTED]> writes:
Some comments on this
> =item C Parrot_Int len, Parrot_String enc)>
>
> Allocates a Parrot_String and sets it to the first C bytes of
> C. C is the name of the encoding to use (e.g. "ASCII",
> "UTF-8", "Shift-JIS"); if a case-insensitive match of this na
Nicholas Clark:
# > The functions for creating and manipulating Cs are
# > listed below.
#
# Is it worth arranging a reminder in here that as parrot is
# garbage collected there is no confusion about who owns
# pointers to blah?
Probably. (Actually, I'd probably put it in a section above thi
On Sat, Aug 17, 2002 at 03:58:32PM -0700, Brent Dax wrote:
> =head2 Strings
>
> Parrot-level Cs are to be represented by the type
> C. This type is defined to be a pointer to a C parrot_string_t>.
>
> The functions for creating and manipulating Cs are listed
> below.
Is it worth arranging a r
