Re: goad status

> redefining goad should break binary compatibility just a bit. 
> Maby the best thing to do would be to seperate goad from libgnorba after
> the 1.0.50 release. The orbit stuff should be able to be done safely now.
> after the orbit fixup, I think goad should be x indemendent
> right away (correct?).

Breaking just a bit is just as bad as breaking entirely.  This is not
an option, and those changes will just be ignored.

And no, GOAD can not be done in a different process, as we need it to
be able to load shared library objects.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]