OpenEuphoria

RE: What we really need...

• Posted by Don Phillips <EuNexus at yahoo.com> Nov 12, 2002
• 427 views

> > Maybe some of it has to do with the web site? I personally think that it
> > could use a bit of tuning up,
> 
> Isnt that funny, I said the very same thing years ago.
> Get rid of the "PINK" on the site and the "Gay" swash
> that resides around the Euphoria name. and things may pickup
> BTW, No offence to the openly Gay community.

Naa, some of my most popular sites which contain really top notch 
software that I frequent have *horrible* websites.  I dont *go* there 
for the web site.  I go there for the software.  I could care less how a 
particular page looks.

> 10) And Don Phillips EuNexus Project or MEdit
>        a) ofcource Don would need to get rid of that MSC .dll he uses

a) <<-- Hah!  Fat chance =)

Main reason why... convenience.  Win32Lib does a superb job of hiding 
the details of what is going on behind the scenes.  API programming is 
not for the faint of heart.  There are more constants, data types, and 
structures than you can shake a stick at.  I have one file at home 
*one*, which is about 55k full of nothing but constants.  Nothing else.

Point?  It is easier for me to code API in just about any other language 
than Euphoria because of structure support.  Heck, the top three 
assembly languages I use all have structures.  I find it unfortunate 
that Windows is so reliant on these things.  I find it even more so that 
Euphoria does not directly support them.

Trying to program API structures with Euphoria is like pulling teeth.  
If done directly via peeks and pokes, its nice and fast.  Its also hard 
to read and maintain.  You can use a library to hide the details (many 
to choose from; I even have my own), but you trade readability for 
speed.  I needed both for the editor portion thus the code resides in a 
DLL.