1. network tools
is there anyway of using euphoria as a network tool maybe
to find holes or make utilities for the internet or networks?
2. Re: network tools
Felecia D. Smith asks:
> is there anyway of using euphoria as a network tool maybe
> to find holes or make utilities for the internet or networks?
This will be a lot easier to do with the WIN32 version
of Euphoria (coming in two weeks). You'll be able to
access networking-related .DLL's (dynamic link libraries)
from Euphoria.
Regards,
Rob Craig
Rapid Deployment Software
3. Re: network tools
On 22 Oct 97 , Robert Craig wrote:
>
> Felecia D. Smith asks:
> > is there anyway of using euphoria as a network tool maybe
> > to find holes or make utilities for the internet or networks?
>
> This will be a lot easier to do with the WIN32 version
> of Euphoria (coming in two weeks). You'll be able to
> access networking-related .DLL's (dynamic link libraries)
> from Euphoria.
Yes, yes, yes !!! This will be the looongest two weeks in my life.
How stable is this alpha version Rob?
I remember some time ago we had a discussion about how this new
version will work... I still have a doubt: If ex32.exe (I guess that
would be a nice name for the interpreter) will be a console
application, would it be possible to create Windows GUI stuff (using
system dll's) without having the console box open (or minimized)?
Will you provide some basic interface to Windows GUI, or should we
(3rd parties) develop them?
Is it coming with some short (but useful) tutorial about Windows
programming?
Will it run only on Win95 or can support WinNT?
Regards,
Daniel Berstein
danielberstein at usa.net
http://www27.pair.com/daber/architek
4. Re: network tools
At 05:47 PM 10/22/97 UT, you wrote:
>
>This will be a lot easier to do with the WIN32 version
>of Euphoria (coming in two weeks). You'll be able to
>access networking-related .DLL's (dynamic link libraries)
>from Euphoria.
>
>Regards,
> Rob Craig
> Rapid Deployment Software
If this is the case, you should at least have an alpha-version ready for
distribution! :)
5. Re: network tools
This is going to be a looonng two weeks.
>---------------------------------------------------------------------------
----
>
>At 05:47 PM 10/22/97 UT, you wrote:
>>
>>This will be a lot easier to do with the WIN32 version
>>of Euphoria (coming in two weeks). You'll be able to
>>access networking-related .DLL's (dynamic link libraries)
>>from Euphoria.
>>
>>Regards,
>> Rob Craig
>> Rapid Deployment Software
>
>If this is the case, you should at least have an alpha-version ready for
>distribution! :)
6. Re: network tools
------ =_NextPart_000_01BCDFE3.828C1500
> This is going to be a looonng two weeks.
Yes. For sure, and not only for you!.
Jesus. (Anxiously waiting...)
------ =_NextPart_000_01BCDFE3.828C1500
7. Re: network tools
- Posted by Robert Craig <rds at CLASSIC.MSN.COM>
Oct 23, 1997
-
Last edited Oct 24, 1997
Daniel Berstein asks:
> How stable is this alpha version Rob?
It should be stable in the sense of not having
too many bugs (I hope), but it still needs a lot of features
before it becomes an official release.
> I remember some time ago we had a discussion about how this new
> version will work... I still have a doubt: If ex32.exe (I guess that
> would be a nice name for the interpreter) will be a console
> application, would it be possible to create Windows GUI stuff (using
> system dll's) without having the console box open (or minimized)?
Actually the WIN32 interpreter is called exw.exe.
In the alpha release there will be a console window, but your program can
also make a regular window pop up and use that instead. Debug/trace will
still be in the console window.
> Will you provide some basic interface to Windows GUI, or should we
> (3rd parties) develop them?
I'm counting on 3rd parties like you and others who have access to WIN32
documentation to make easy-to-use Euphoria libraries in many application
areas. RDS will also do this, but WIN32 is so big we can't do it all by
ourselves.
> Is it coming with some short (but useful) tutorial about Windows
> programming?
There's a short tutorial on how to use the WIN32 version, plus there
are small demo programs that pop up windows, do graphics in a window,
play .WAV files, send e-mail messages over the Internet etc.
> Will it run only on Win95 or can support WinNT?
The WIN32 API is supported by Win95 and WinNT with only minor
incompatibilities. It's easy to make a program that works on both
platforms.
Some further info:
* The release will be called Euphoria 2.0 (alpha)
* Euphoria will not be split into two separate products. There will be
a single .ZIP that supports 2 platforms - DOS32 and WIN32.
The .ZIP will install and will have ex.exe (DOS32) and
exw.exe (WIN32) in euphoria\bin. You can use whichever
interpreter you want for your particular application. ex.exe is
better than exw.exe for games and fast text-mode screen updates.
Many of the include files can be shared by the two platforms.
* Most plain text-mode programs will run on either platform with the
same results. e.g. ed.ex and lw.ex both run the same but are
slower under exw.exe.
* "pointers" to functions/procedures are now supported in both
platforms.
You can get a "pointer" to a routine, actually an integer known as a
"routine identifier" and store it, pass it to another routine etc.
This eliminates the mutual recursion restriction. You can
effectively
call routines that come later in the source by using their routine
id.
* new library routines, e.g. peeking and poking 4-byte atoms etc.
have been added for both platforms, plus several other minor
improvements.
If you don't have access to WIN32 documentation your ability to use
the WIN32 alpha will be limited. It will become more usable as we develop
the beta and final versions and 3rd parties start to contribute things.
You'll be able to register for the 2.0 DOS32 Complete Edition at the same
$32 price as before (no increase in 4 years!), or for $21 extra you can
register for
*both* the DOS32 and WIN32 Complete Editions. i.e. you'll get the
fully-enabled
ex.exe and exw.exe. You won't be able to register for just WIN32 by itself.
If you register or upgrade to 1.5a during the alpha/beta testing period you
will be able to
download alpha, beta and final of 2.0 for whichever platform(s) you purchase.
You'll
also get 1.5a, the current official release.
If you register or upgrade to 1.5a from now until the alpha release
(a couple of weeks away) we'll let you download 2.0 DOS32 platform
alpha/beta/final for free (but not WIN32 platform). You'll also get 1.5a of
course.
As for printed manuals, you'll get 1.5a unless you tell us that you
want to wait until the 2.0 final release.
Regards,
Rob Craig
Rapid Deployment Software
8. Re: network tools
- Posted by Greg Harris <blackdog at CDC.NET>
Oct 23, 1997
-
Last edited Oct 24, 1997
>> Will you provide some basic interface to Windows GUI, or should we
>> (3rd parties) develop them?
>
>I'm counting on 3rd parties like you and others who have access to WIN32
>documentation to make easy-to-use Euphoria libraries in many application
>areas. RDS will also do this, but WIN32 is so big we can't do it all by
>ourselves.
Just a quick question....
Will the Win32 version support .OCXs or ActiveX .dlls? I believe that
ActiveX .dlls are compatible with regular .dlls but I could be wrong. That
would be great for us C declined people. Any info would be appreciated.
Thanks,
Greg
9. Re: network tools
Greg Harris asks:
> Will the Win32 version support .OCXs or ActiveX .dlls? I believe that
> ActiveX .dlls are compatible with regular .dlls but I could be wrong. That
> would be great for us C declined people. Any info would be appreciated.
I assume so, but I will look into this after I
get the alpha release out.
Philip A Lettkeman asks:
> Wil the DOS32 version be able to make dos level library calls. Say to
> libraries made with Borland Turbo C or Visual C++ 1.52?
No. Support for .DLLs is only in the WIN32 version.
Mike Burrell proposes:
> data = {}
> fn = open("blah.exe", "rb")
> tempo = gets(fn)
> while sequence(tempo) do
> data = data & tempo
> tempo = gets(fn)
> end while
> addr = allocate(length(data))
> poke(addr, data)
> call(addr)
> something like that? although i would personally do a system()
No, it's not that easy. A .exe file is not just a bunch of machine code.
There's other information in there too. Loading a .exe into memory
and running it is fairly complicated.
Regards,
Rob Craig
Rapid Deployment Software
10. Re: network tools
Mike Burrell proposes:
> data =3D {}
> fn =3D open("blah.exe", "rb")
> tempo =3D gets(fn)
> while sequence(tempo) do
> data =3D data & tempo
> tempo =3D gets(fn)
> end while
> addr =3D allocate(length(data))
> poke(addr, data)
> call(addr)
> something like that? although i would personally do a system()
Robert Craig answered:
>No, it's not that easy. A .exe file is not just a bunch of machine code.=
>There's other information in there too. Loading a .exe into memory
>and running it is fairly complicated.
>Regards,
> Rob Craig
>Rapid Deployment Software
What Mike proposes, is possible with .com files, I think. Assemblers can
produce .com files, but I don't know if C(++) or other compilers can. But=
in that case a system() call from Euphoria would still be preferable.
Ad_Rienks at compuserve.com
