Re: dll strangeness
- Posted by DerekParnell (admin) Aug 14, 2010
- 1283 views
... switching to Eu4 0, I am having to change many things, from something as simple as this line:
elsif c <= KEYWORDTOP and c> 0then - plug in keyword
that no longer works and so I switch to:
elsif c <= KEYWORDTOP and c> 0 then - plug in keyword
In V4, a numeric literal must be terminated by whitespace, punctuation, or end-of-line. We can no longer merge numeric literals and words together. This will assist in making source code more readable for people.
If I had my way, I'd also insist that operators such as '<', '=' etc... not be allowed to be right next to identifiers. I'm committed to the idea that programming languages are primarily for people to read and write, so therefore making code easier to read is a priority.
As I also have to resolve things more complicated, such as producing a "file.exe"
The transition Eu311>>Eu4 would be simpler if the Eu4.0 uses its own environment variables and not those of Eu311
For example, if the variable EUDIR and EUINC remained restricted to the use of Eu311, this version would continue running smoothly.
You can do this already.
- Keep the EUDIR and EUINC environment variables pointing to the Eu3 folders
- Create a text file called 'eu.cfg' in the same directory as the Eu4 executable files.
- In 'eu.cfg', list the Eu4 folders (one per line) where you want it look for include files.
For example,
-- eu.cfg -- c:\eu4\include .\include ..\include -- end of eu.cfg --
Now, when Eu3 runs, it will only look at EUDIR and EUINC, and when Eu4 runs, it will look in the folders named in eu.cfg and if the include file is not found in those folders, Eu4 will use EUDIR and EUINC.
