OpenEuphoria

Re: File Extensions (again)

• Posted by Greg Haberek <ghaberek at ?mail.c?m> Apr 25, 2008
• 583 views

Jeremy Cowgar wrote:
> 
> e - include
> ew - include on windows
> eu - include on unix
> ex - dos executable
> exw - windows executable
> exu - linux executable
> 
> 
> Now, where I am running into problems is what is executable for dos, windows
> and unix all in one file? i.e.

I think we need to move away from the concept of such explicit extension usage.
One may find himself lost (as I'm sure you are now) if one expects an extension
alone to determine the platform of the source. Here's my concept of our existing
file extensions:

.e - basic libraries, generic code that most everything can use
.ew - advanced libraries, GUI elements or dynamic library wrappers
.eu - Unix-specific libraries, code which will not work on DOS or Windows
.ex - command-line or DOS applications
.exw - GUI applications
.exu - Unix-specific applications

In a perfect world, .ex and .exw files would be 100% cross-platform. I've rarely
come across code that I've written on Linux that won't work on Windows or DOS
with a few extra calls to platform(). I can't remember the last time I've used
.eu or .exu on a project, if ever.

-Greg