On 29 November 2012 00:58, Camillo Bruni <[email protected]> wrote: >>> On 28 November 2012 22:24, Ciprian Teodorov <[email protected]> >>> wrote: >>>> Hi guys, >>>> >>>> Looking at NB methods extending Object I am wandering if it won't be >>> better >>>> to put them in a Trait to be used by any class needing them? >>>> >>> i don't see what you will gain from that, except that you will end up >>> using that trait >>> all over the places? >>> >> What do you understand about all over the places? In my opinion FFI calls >> should be very well isolated >> in specific modules that are meant for that. I think we might have >> different views on this issue... I see using external libraries >> as a limited number of classes (maybe just one in most cases) doing the >> native calls, and then writing a library that relies on these classes >> only for calling the external library. This way the external interfaces are >> well defined, and we don't run the risk of having the whole image full of >> FFI calls... > > I think so too, traits would help limiting the scope of FFI. > > maybe the tools could require some polish, but not using traits won't help ;) > every time one using double negation, a small kitten dies.
so, please clarify your statement :) -- Best regards, Igor Stasenko.
