On Mon, Sep 30, 2002 at 02:24:06PM +0200, J?r?me Marant wrote: > On Mon, Sep 30, 2002 at 02:22:59PM +0200, Maxence Guesdon wrote: > > > > > > Hum, yes, but not for all. For example, cameleon native and bytecode > > > > versions differ because the bytecode version allows the plug-in > > > > loading, but native version is faster. For tools where native and byte > > > > code versions do the same, I agree that I should only compile byt OR > > > > native. I'll do this in the future. > > > > But keeping bytecode AND native is good, isn't it ? > > > > > > If there aren't any good reason for keeping both, users won't > > > understand. > > > Are cameleon binaries the only ones to behave differently in Cameleon? > > > (BTW, what binaries from the cameleon directory behave a different way?) > > > > Excuse me, i forgot a part of the sentence : > > But keeping bytecode AND native *FOR LIBRARIES* is good, isn't it ? > > > > This is _way_ different :) I strongly agree with you about libraries.
For libraries, you have to ship both, i think the policy says this, but i am not sure, will check. Friendly, Sven Luther
