- Since Active4D 2004 will be byte-compiled, the language will be a little stricter.
Having been through transitions like this in the future, something that would be *very* helpful is an option in an interim .x release that enforces these rules, so we can flush the problems out of existing code in advance.
Unfortunately that won't be possible, because the whole thing is basically being rewritten from the ground up. As long as you follow these rules, you should have no problem with the transition:
- Declare all local arrays before use.
- Local non-array variables must either be declared with a compiler declaration or appear on the left side of an assignment before being referenced. Variables will still be variant in type by default.
- 4D Methods must exist before being referenced.
- Active4D methods must be declared before being referenced. For library methods this is nothing new, as importing will occur at compile time. If you are referencing a method in an included file, the include filename must be a literal string and the include statement must not be within a control structure.
If I think of any other restrictions I will let everyone know.
Regards,
Aparajita Victory-Heart Productions [EMAIL PROTECTED] www.aparajitaworld.com
"If you dare to fail, you are bound to succeed." - Sri Chinmoy | www.srichinmoylibrary.com
