RE: wishlist

new topic     » topic index » view thread      » older message » newer message

I think 2,3,4 are operating system specific and shouldn't *have* to be 
included in the language itself; in dos you can call "system" and in windows 
the specific functions from whatever DLL involved to do this. You could wrap 
your own functions but I doubt they'd really need to be included in the 
language itself.

It's very easy to get around a defined symbol using an euphoria data type, 
though I admit it would make some aspects of code cleaner

>here are some things that'd be cool to put in eu...
>
>1) an "ncurses" option for the without keyword to use basic console I/O
>without initializing ncurses. i have a program i'm writing with Irv's
>GraphApp wrapper. When someone clicks the menu and then selects Close or
>Delete or whatever, the window will close and exu will shutdown, but if
>it was launched from the console, outside of ncurses, no color will be
>seen, nothing typed will be echoed, and carriage returns don't do
>anything
>
>2) Defining symbols. For example:
>
>--- somefile.e
>if somecondition then
>  define get_a_life
>end if
>..
>
>-- main.ex
>include somefile.e
>
>if defined(get_a_life) then
>  puts(1,"You need a life. How many can I put you down for? ")
>..
>
>3) A rename() function:
>
>result = rename("afile","anewfilename")
>
>4) A set_attributes() function:
>
>result = set_attributes("afile","744")
>
>or
>
>result = set_attributes("afile,"rwxr--r--")
>
>or in DOS/Windows
>
>result = set_attributes("afile","+a-h") -- set archive, unset hidden
>
>or in any upcoming Macintosh port...
>
>result = set_attributes("afile",{"APPL","????",0})
>
>where the first item is the file type, the second is the creator, and
>the third indicates if the file is locked.
>
>5) Maybe even the ability to use .o and .a files in Linux and .lib and
>.obj files in DOS
<snip>

>

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu