On Monday 17 May 2004 23:14, you wrote:
> Should I stick with library/ or runtime/include/?
I vote for runtime/parrot/library/SDL
The paths currently in use are going to stay valid this way.
FWI, runtime/parrot/perl6 et al can hold language specific libraries (if a
language does not use its own d
On Mon, 2004-05-17 at 14:12, Jens Rieks wrote:
> > It's ok for me.
> The patch is in.
>
> The SDL stuff now works without any special environment variables.
Unless someone hollers in the next day or two, I'll check in the new
libraries and examples.
Should I stick with library/ or runtime/inclu
Hi,
On Monday 17 May 2004 15:07, Leopold Toetsch wrote:
> > Should I apply it?
>
> It's ok for me.
The patch is in.
The SDL stuff now works without any special environment variables.
jens
Jens Rieks <[EMAIL PROTECTED]> wrote:
> whats the plan WRT to CALL__BUILD?
> I've written a patch that makes it the default, but does a fallback to
> "__init" if no BUILD property is set.
[ ... ]
> Should I apply it?
It's ok for me.
> jens
leo
Hi,
whats the plan WRT to CALL__BUILD?
I've written a patch that makes it the default, but does a fallback to
"__init" if no BUILD property is set. If the __init method does not exists,
no exception is thrown (like before), whereas now an exception is thrown if
you specify a BUI
