A trait would be perfect for this, but your not allowed to use traits in platform-specific code, for administrative reasons.
I guess an include is better than code duplication. On 2006-07-21, at 12:37 EDT, Henry Minsky wrote: > > I have some common code between two kernel implementations of the > same API, LzHTTPLoader.as and LzHTTPLoader.js. Where > should I put the common code? It's code that is portable so that > would put it someplace in the LFC, but it is used by kernel code. > I am not sure how to structure this -- the LHTTPLoader.as and .js > files define their own LzHTTPLoader objects and put methods > on them. > > I'm thinking that this code could go into lfc/kernel, and be > #included by the individual runtime files (lfc/kernel/swf/ > LzHTTPLoad.as, and > lfc/kernel/dhtml/LzHTTPLoader.js) > > > -- > Henry Minsky > Software Architect > [EMAIL PROTECTED] > _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
