I'm looking in my agenda but no options this week. If you're looking for LessTif work, then look at the bugs database. I believe there's a binary compat bug in there related to Bristol's Hyperhelp product. I was never able to track that.
I'm working on bug 993209, no need to take that one.
Other things to do that come to mind :
- implement more traits
- implement the functions that are empty or that generate
a warning saying they don't do anything
- make LessTif thread-safe
Ciao,
Danny
On Fri, 2005-04-01 at 14:32 +0200, Michel Bardiaux wrote:
> Danny Backx wrote:
> > I'll update the docs.
>
> In what direction?
>
> > But supporting binary compatibility may not be
> > trivial. We'll see how far we get.
> >
> > Danny
> >
> I understand that. Note that I stopped any contribution to Lesstif
> because I didnt agree with the source-compat objective. If there is work
> to be done towards binary compatibility, count me in, and send me some
> suggestions of things to do.
>
> Of course, since Motif broke ABI compat when going from 2.1 to 2.2, one
> *might* say the strategy should be 2.1 API first, then 2.2 API, then 2.2
> ABI...
>
> Cheers,
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
signature.asc
Description: This is a digitally signed message part
