OpenEuphoria

Re: 4.0 breaks all the code in the archive.

• Posted by Jeremy Cowgar Jul 17, 2008
• 785 views

Yes, the current SVN will break all existing code. Yesterday we moved all files from C:\EUPHORIA\INCLUDE to C:\EUPHORIA\INCLUDE\STD. Thus, any existing program that does anything like

include machine.e 

will fail w/o doubt.

Now, the good thing about this is that once all of 4.0 is updated to use the new std/ directory, we will be adding in all 3.1.1 include files into C:\EUPHORIA\INCLUDE directory. This means that any 3.x program will find all of it's standard files w/o changing one thing. The libraries will be added unchanged and not dependent upon any of the new 4.0 standard library. This will ensure that the vast, vast majority of 3.x apps will run under 4.0 w/o any change.

The only thing that will break an old 3.x program is if you have used a variable or routine by the same name as a new keyword and, for that, we are working on a conversion program. For instance, it will scan your source, look for variable/routine names by the name of any new keyword (label, entry, break, switch, case, etc...) and will alter their usage to be label_var or label_routine, etc... Not nice names, but you can then name the as you wish. This should allow any 3.x program to run under 4.0 with out editing code.

This is indeed a good thing.

Now, you found the repository in a state that is in transition. We did not want to add the 3.1.1 includes yet as it may mask an existing 4.0 program, demo, tutorial, utility or whatever. If we forgot any include machine.e to include std/machine.e than 4.0 would be dependent upon the 3.1.1 includes which we do not want. So, for the next few days, no 3.1.1 includes will be in the repo. This will break all existing applications for sure. Sorry for this interim process but the end result is going far outweigh the week we are w/o 3.1.1 compatability.

Jeremy Cowgar