1. Win Euphoria?
I meant Windows Euphoria, not win (as a prize) Euphoria, though that would
be nice too.
Anyway, just a few questions:
* What will Win Euphoria offer? Will it be design oriented, like VB or VC++,
or will it act like regular old DOS Euphoria and run the same programs but
in Win95? (Hoping for the latter!)
* Will it offer support for DirectX? This is a long shot, I know.
* Will it offer access to DLLs and the Windows API?
* Will it be event oriented or still a scripting language?
The reason why I ask all this is I write in VB and loathe the messaging
system it employs. Euphoria is the last best hope I have for a modern
language that is still a scripting language -- especial-mont in Windows.
Cameron Kaiser
http://www.sserv.com/
spectre at sserv.com
2. Win Euphoria?
Excuse me if you see two copies of this message, but after
38 hours I have not received any acknowledgement from
the list server, so I'm reposting it. I suspect
CompuServe is having problems with outbound mail again.
-- Rob Craig
-----------------------------------------------------------
Cameron Kaiser asks:
> * What will Win Euphoria offer? Will it be design oriented, like VB or VC++,
> or will it act like regular old DOS Euphoria and run the same programs but
> in Win95? (Hoping for the latter!)
It will be more like the latter.
> * Will it offer support for DirectX? This is a long shot, I know.
Maybe.
> * Will it offer access to DLLs and the Windows API?
Definitely.
> * Will it be event oriented or still a scripting language?
I'm not sure what the definition of a "scripting" language is.
The first release of Euphoria for WIN32 will let you call
C routines in 32-bit DLLs. These could be WIN32 API routines,
or compiled C DLLs that you or someone else has written.
We're hoping that 3rd party developers will provide lots of add-ons
that are written in C and can be called from Euphoria by people who don't
know C or Windows. We will also write add-on DLLs.
All plain text-mode Euphoria programs that run today using the
32-bit DOS ex.exe will run under WIN32 Euphoria. As for graphics,
we'll see what we can support. Things like dos_interrupt() calls
aren't going to work on WIN32. Many programs such as ed.ex,
search.ex and language wars are already working, i.e. the same
source code can be run by the
current DOS ex.exe or by the WIN32 ex.exe with identical output.
The WIN32 ex.exe runs as a "Windows console application" when it
runs this type of program, i.e. a DOS-prompt-like window appears,
and you can run the WIN32 ex.exe from a command prompt, just like
you run the DOS ex.exe now.
The release of the Windows version of Euphoria will NOT mark
the end of the DOS version. There will simply be 2 versions
of ex.exe that you can choose from. If you don't need
any WIN32 routines then the DOS version will be a
better choice for most applications. For example, the
output of text to a window is slower under WIN32
than under DOS.
We expect that the WIN32 version will initially be rather
primitive, but will grow with 3rd party support. The DOS
version will continue to be enhanced, and in fact, most
of the ex.exe source code, including the entire core language, and
most of the library routines, is shared between the two versions.
When is the WIN32 alpha release coming? A few months. I don't want to
be any more precise than that. Registered users of the DOS version
will get some kind of discount on the WIN32 version. We haven't
decided on pricing, but there will be a Public Domain (free) version.
Regards,
Rob Craig
Rapid Deployment Software
3. Re: Win Euphoria?
> The WIN32 ex.exe runs as a "Windows console application" when it
> runs this type of program, i.e. a DOS-prompt-like window appears,
> and you can run the WIN32 ex.exe from a command prompt, just like
> you run the DOS ex.exe now.
i was kind of hoping for something nearer the "visual" side of things
(i.e. VB or VC++)... i mean what will the win32 version offer that
the dos version won't if they're essentially the same language... i
think the TYPEs in euphoria already show signs that euphoria could
become object oriented... i know asking for interface designing
abilities like VB's is probably too long of a shot to ask for, but
there should still be the ability to make "normal" windows
applications with euphoria, right??
. o O Mike Burrell O o .
. o O http://www.geocities.com/SoHo/9036 O o .
. o O burrellm at geocities.com O o .
4. Re: Win Euphoria?
- Posted by Robert Craig <robert_craig at COMPUSERVE.COM>
Apr 09, 1997
-
Last edited Apr 10, 1997
Mike Burrell writes:
> there should still be the ability to make "normal" windows
> applications with euphoria, right??
Yes, that's our intention, but
we don't expect to drive Microsoft Developer Studio
off the market with our first release. 
Regards,
Rob Craig
Rapid Deployment Software
5. Win Euphoria?
- Posted by Robert Craig <robert_craig at COMPUSERVE.COM>
Apr 07, 1997
-
Last edited Apr 08, 1997
Cameron Kaiser asks:
> * What will Win Euphoria offer? Will it be design oriented, like VB or VC++,
> or will it act like regular old DOS Euphoria and run the same programs but
> in Win95? (Hoping for the latter!)
It will be more like the latter.
> * Will it offer support for DirectX? This is a long shot, I know.
Maybe.
> * Will it offer access to DLLs and the Windows API?
Definitely.
> * Will it be event oriented or still a scripting language?
I'm not sure what the definition of a "scripting" language is.
The first release of Euphoria for WIN32 will let you call
C routines in 32-bit DLLs. These could be WIN32 API routines,
or compiled C DLLs that you or someone else has written.
We're hoping that 3rd party developers will provide lots of add-ons
that are written in C and can be called from Euphoria by people who don't
know C or Windows. We will also write add-on DLLs.
All plain text-mode Euphoria programs that run today using the
32-bit DOS ex.exe will run under WIN32 Euphoria. As for graphics,
we'll see what we can support. Things like dos_interrupt() calls
aren't going to work on WIN32. Many programs such as ed.ex,
search.ex and language wars are already working, i.e. the same
source code can be run by the
current DOS ex.exe or by the WIN32 ex.exe with identical output.
The WIN32 ex.exe runs as a "Windows console application" when it
runs this type of program, i.e. a DOS-prompt-like window appears,
and you can run the WIN32 ex.exe from a command prompt, just like
you run the DOS ex.exe now.
The release of the Windows version of Euphoria will NOT mark
the end of the DOS version. There will simply be 2 versions
of ex.exe that you can choose from. If you don't need
any WIN32 routines then the DOS version will be a
better choice for most applications. For example, the
output of text to a window is slower under WIN32
than under DOS.
We expect that the WIN32 version will initially be rather
primitive, but will grow with 3rd party support. The DOS
version will continue to be enhanced, and in fact, most
of the ex.exe source code, including the entire core language, and
most of the library routines, is shared between the two versions.
When is the WIN32 alpha release coming? A few months. I don't want to
be any more precise than that. Registered users of the DOS version
will get some kind of discount on the WIN32 version. We haven't
decided on pricing, but there will be a Public Domain (free) version.
Regards,
Rob Craig
Rapid Deployment Software
