> It'll probably be more like: > > void *name = Get_String_Data(p1, PARROT_UNICODE, encoding); > > And yes, the void * is deliberate (though subject to change) since I'm > being generic--how do you know that you're getting back a series of bytes? > encoding might have the UTF_32 constant in it. Isn't *everything* a series of bytes? :-) > For just fetching the abstract string structure it'd be more like: > > Parrot_string *name = Get_String(p1); > > FWIW, anyone using char * in the Parrot source in areas that do not > directly involve interface with the external world (system calls, other > people's libraries) will find themselves on the other end of the Big Mallet > of Programmer Chastisement. :-) Sure, but please explain. --Guido van Rossum (home page: http://www.python.org/~guido/)
- Re: Anachronistic Acronyms in Parrot? Simon Cozens
- Re: Anachronistic Acronyms in Parrot? David Beazley
- Re: Anachronistic Acronyms in Parrot? Donal K. Fellows
- Re: Anachronistic Acronyms in Parrot? Dave Mitchell
- Re: Anachronistic Acronyms in Parrot? David Cantrell
- Re: Anachronistic Acronyms in Parrot? Andrei Zmievski
- Re: Anachronistic Acronyms in Parrot? Jeremy Hylton
- Re: Anachronistic Acronyms in Parrot? Nathan Torkington
- Re: Anachronistic Acronyms in Parrot? raptor
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Guido van Rossum
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Yukihiro Matsumoto
- Re: Anachronistic Acronyms in Parrot? Paul Prescod
- Re: Anachronistic Acronyms in Parrot? Donal K. Fellows
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Paul Prescod
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Donal K. Fellows
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Donal K. Fellows
