Re: Parrot_get_runtime_prefix has a bad interface

2007-06-22 Thread chromatic
On Saturday 16 June 2007 23:41:30 Andy Lester wrote: > I cringe at functions where the behavior is dependent on parms passed > in. In the case of Parrot_get_runtime_prefix, if you call it as > Parrot_get_runtime_prefix(&str) then str is populated, or if you call > Parrot_get_runtime_prefix(NULL)

Re: Parrot_get_runtime_prefix has a bad interface

2007-06-17 Thread Mike Mattie
On Sun, 17 Jun 2007 01:41:30 -0500 Andy Lester <[EMAIL PROTECTED]> wrote: > I cringe at functions where the behavior is dependent on parms > passed in. In the case of Parrot_get_runtime_prefix, if you call it > as Parrot_get_runtime_prefix(&str) then str is populated, or if you > call Parrot_get_

Parrot_get_runtime_prefix has a bad interface

2007-06-16 Thread Andy Lester
I cringe at functions where the behavior is dependent on parms passed in. In the case of Parrot_get_runtime_prefix, if you call it as Parrot_get_runtime_prefix(&str) then str is populated, or if you call Parrot_get_runtime_prefix(NULL) then you get a malloced string. It should be split int