Re: Euphoria file types
- Posted by jeremy (admin) Mar 06, 2009
- 1336 views
I see it differently.
| Extension | Interpreter | Reason |
|---|---|---|
| .ex | exwc, exu | console/server application |
| .exw | exw, exu | windowed (as in GUI, not as in Windows) application |
| .exd | ex | DOS application |
| .e | - | include file |
My thinking on these lines is:
- DOS is the odd ball now. Maybe 10 years ago it was the standard, but times have changed. Yes, some people still use DOS but I can find 10,000 people who use Windows/Linux/OS X for every 1 that uses DOS.
- Euphoria is a cross platform language and is growing so even more. With 4.0 we now have OS X support.
- For those scripts that are platform dependent, do we really want the extension to indicate this? It has no enforcement. For instance, I can run exwu myfile.txt, or exw hello.ruby. As long as it's Euphoria code, Euphoria does not care about extension of the source file, so an extension enforces nothing. Further, do we really want ex=DOS, exw=Windows, exu=Unix/Linux, exfb=FreeBSD (it is different than Linux), exosx=OS X. Further, being cross a cross platform language, many of these applications could care less what platform they are running on.
- Euphoria scripts can easily check what platform they are running on and if they do not support OS X or they require Windows, then the application should state so in code, as the application executes.
- Many applications now use cross-platform GUI libraries. We have Gtk, wxWidgets, Iup and even EuQT (just a start, but it is already more functional than other languages Qt wrappings). These applications are "windowed" or "GUI" application but will run on Windows, Linux, FreeBSD and OS X w/o change.
- Euphoria, as far as I know, has been the only language to make the distinction of platform in their file extensions. For instance, you do not have luad (DOS), luaw (Windows), luao (OSX), luau (Unix), etc.. Nor rbd, rbw, rbo, rbu for Ruby, or pyd, pyw, ... for Python.
- We need to make some distinction because we have three interpreters on the Windows platform (DOS (ex), Console (exwc), No Console (exw)).
The above plan makes the standard extensions hit the widest target.
Jeremy
