CALL__BUILD

[Jens Rieks]

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 BUILD property and the specified method does not exists.
A special case is if you set BUILD to an empty string, then no constructor is
called for the class, not even __init if it exists.

All tests are passing, plus two new tests for the new functionality (exception
if constructor not found and constructor disabling)

Should I apply it?

jens

[Leopold Toetsch]

Jens Rieks <par...@jensbeimsurfen.de> 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

[Jens Rieks]

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

[Chromatic]

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/include/<whatever>?

-- c

[Jens Rieks]

On Monday 17 May 2004 23:14, you wrote:
> Should I stick with library/ or runtime/include/<whatever>?

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 directory, for example)
runtime/parrot/library should IMO contain all language-neutral libraries.

jens