Re: Starting project EuphoriaVista Interpreter
- Posted by jcmarsh1 Jan 02, 2009
- 1319 views
Euphoria for Vista Concerning the Win32 distribution of Euphoria v3.1.1 and v4.0
Things I know through trial or error:
- Interpreter will not work under DEP (yet), work is under way.
- It should only run under DEP for security reasons and system stability
- To make it run under DEP new code will have to be added to the source (pending)
- The executable (with DEP) would only be useful on Vista (I believe) unless there is code that detects previous versions and lets them run skipping the DEP code.
- If this executable will only be used on Vista, it could make use of other newer features that are only found on Vista or later.
I suggest that the Windows Distribution be split into three (3) main parts:
- DOS32 and Win98 compatible (designed to run on Win98)
- WinNT/2000/XP compatible (designed to run on WinXP with Win2000 support using exw) (Note: ex is only supported by WinXP using a backwards compatibility layer that is dropped from later version of Windows)
- Vista compatible (designed to run on Vista, exw only--ex will crash it is unsafe on Vista)
- It should be noted that ex.exe is only fully supported on Win98 (and earlier) and only mostly supported on WinXP
The libraries for Windows functions would also need to be split up accordingly as jimcbrown suggested.
The libraries could contain API functions in groupings as follows:
- functions as old as Win3.1 API and as new as Win98 in winlib98.ew or w32lib98.ew (8.3 filename for backwards compatibility) -- these would be for the Win98 package
- functions as old as NT 4.0 and as new as WinXP (that are only in the WinNT branch of the API) in winnt32lib.ew or winxp32lib.ew -- these would be for the Win2000/XP package
- functions as old as Vista (and newer) in vista32lib.ew
- Vista 64-bit support will have to wait until the source can compile for 64-bit on IA64 (Intel) and x86-64 (such as AMD64) architectures
These are all suggestions. I will be looking forward to any feedback.
