|
You can use #include statement the same way you
would use it in C. That pretty much solves the issues of code separation. The
way you slice it is very much up to your preferences - as it does not
really serves the code partitioning, but rather readability
purposes.
The fun begins when you decide to abandon static
code linkage and go dynamic. That is important in the event when you develop
application thet would be dynamically configured by the end-users. You need to
package your software in a way it can be assembled in the run-time - with
minimal overhead.
That very much call for usage of RSLs for large
components, data-driven UI and ability to dynamically create/cache compiled
code. Depending if you are interested in "readability" or "dynamics" of the code
different solutions can be derived
Here is the brief internal training video of the
component that utilizes dynamic classes :
http://demo.xmlsp.net/dataservice%206/dataservice%206.html Hope this helps,
Anatole Tartakovsky
|
- Re: [flexcoders] Spltting up code (best practice) Anatole Tartakovsky
- RE: [flexcoders] Spltting up code (best practice) Jonathan Miranda
- Re: [flexcoders] Spltting up code (best pract... Anatole Tartakovsky
- Re: [flexcoders] Spltting up code (best p... Teoti Graphix
- Re: [flexcoders] Spltting up code (be... Anatole Tartakovsky

