OpenEuphoria

RE: fixed windows

• Posted by kbochert at copper.net Aug 06, 2003
• 382 views

On 5 Aug 2003 at 14:06, gertie at visionsix.com wrote:

> >     So I really don't understand what you mean by "merging Eu and
> >     mIRC" ?! They are two completely different things. It's like
> >     asking to merge Visual Basic (a language) with OpenOffice (as
> >     a scriptable application).
> 
> In a word(s):
> 
> mirc:
> 1) executing strings
I have lately come to realize that this is not that hard in Bach.
Bach 2 has already laid the groundwork by changing the way source
is handled internally.

> 2) goto
This belongs in the group below as well.
for me, goto is essential in writing something like
thr interpreter. I have not once found a situation
in Bach where it would help.

> 3) threads (including threaded timers)
Bach 2 does have coroutines which allow cooperative
multitasking. Not quite the same thing, but its a start.

Another feature which I have lately realized is quite
doable is child processes:
    child_exec("foo.exe -w")
would operate just like system_exec(), except that
the child process would have its stdio redirected
to the parent.
Is this old hat?
Is there a Eu library that does this?

> 4) event handling
You could write your program as an event loop that
calls a series of coroutines. One coroutine detects
events, another responds to them.
Still not pre-emptive but if you don't need realtime...

> 5) native socks support (you can http/telnet/pop3 with mirc too)
Bach will interface to TCP4U. Does this provide enuf?

> 6) easy as heck gui support
> 7) no var instanciation required
I have great difficulty with languages that allow this.
Having the data spelled out with declarations is
crucial to my understanding of that program.

> 8) no crash if a var has no contents in a boolean test
In Bach, variables that are part of a class are automatically
initialized, so a statement like:
   if  Cls.cnt = 0  then ...
will never crash

> 
> Bach:
> 9) classes
Bach's classes are meant to provide a more powerful
procedural programming environment, not OO!
(I don't comprehend OO)

> 10) crash catching

> 11) gui support
I continue to be amazed at the short learning curve of IUP.

> 12) block comments
Seemed like a frill, but turned out to be very useful. Not only for
commenting out blocks,  but also for documentation blocks.

> 13) slicing shorthands
When I started Bach, this was the first thing on my wish list.
Turns out to be less important than I thought.

> 14) better include paths 
Changed a little in 2.0.
homedir, BACHLIB env var path, BACHDIR\user, BACHDIR\LIB
I was losing track of what was searched, so failure to find an
id displays all files which were tried.
> 
> These 14 items are things BobC has said will not appear in Eu. The closest 
> app i have seen coded in Eu that might enable all the above is AGetz's 
> window server and Jiri's associated lists. And several string libs are
> required
> in my opinion, string.e and strtok.e, and the file manipulation libs like
> file.e,,
> and for any windows gui, you must have win32lib. If RobC can't handle the 
> full developement of Eu, i refer you to my suggestion he hire Jiri, Cuny, and 
> Parnell (maybe paying them in futures, like stock).
> 
> Kat
> 
> --^----------------------------------------------------------------
> This email was sent to: kbochert at copper.net
> 
> 
> TOPICA - Start your own email discussion group. FREE!
> 
>