1. OpenWatcom
I committed some changes to the Euphoria svn repository to fix the source
for OpenWatcom. There's also a makefile (makefile.wat) for building
it using OpenWatcom.
Matt
2. Re: OpenWatcom
- Posted by Robert Craig <rds at RapidEuphoria.com>
Nov 28, 2006
-
Last edited Nov 29, 2006
Matt Lewis wrote:
> I committed some changes to the Euphoria svn repository to fix the source
> for OpenWatcom. There's also a makefile (makefile.wat) for building
> it using OpenWatcom.
Good. I can compile with OpenWatcom, but
I still normally use Watcom 10.6 because
of the "pop up to full screen" issue in DOS.
I'm glad there's a developer using OpenWatcom.
I see you added "EOW".
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: OpenWatcom
--
"Any programming problem can be solved by adding a level of indirection."
--anonymous
"Any performance problem can be solved by removing a level of indirection."
--M. Haertel
"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare
j.
4. Re: OpenWatcom
Robert Craig wrote:
>
> Matt Lewis wrote:
> > I committed some changes to the Euphoria svn repository to fix the source
> > for OpenWatcom. There's also a makefile (makefile.wat) for building
> > it using OpenWatcom.
>
> Good. I can compile with OpenWatcom, but
> I still normally use Watcom 10.6 because
> of the "pop up to full screen" issue in DOS.
> I'm glad there's a developer using OpenWatcom.
> I see you added "EOW".
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
Sorry if the last message shows up; I meant to quote.
What's EOW? That has been bugging me all day.
--
"Any programming problem can be solved by adding a level of indirection."
--anonymous
"Any performance problem can be solved by removing a level of indirection."
--M. Haertel
"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare
j.
5. Re: OpenWatcom
Jason Gade wrote:
>
> Robert Craig wrote:
> >
> > Matt Lewis wrote:
> > > I committed some changes to the Euphoria svn repository to fix the source
> > > for OpenWatcom. There's also a makefile (makefile.wat) for building
> > > it using OpenWatcom.
> >
> > Good. I can compile with OpenWatcom, but
> > I still normally use Watcom 10.6 because
> > of the "pop up to full screen" issue in DOS.
> > I'm glad there's a developer using OpenWatcom.
> > I see you added "EOW".
> >
>
> Sorry if the last message shows up; I meant to quote.
>
> What's EOW? That has been bugging me all day.
>
If you've looked at the source, you've probably noticed several macros
that identify the platform and compiler being used. There are a couple
of places that need to be different from Watcom 10.6 vs Open Watcom 1.5
(be_callc.c and be_runtime.c). I added a new macro (EOW) to specify
that the OpenWatcom compiler is being used. The convention that Rob has
used is to prefix any of his macros with an 'E', so I used that, too.
The makefile is handy, because it only compiles the files that have been
changed. If you make changes to the front end, you may need to change the
makefile. The translator will break up large files, and changes (additions,
deletions, etc) may produce different files. Basically, if any of the
euphoria source files for the front end change, it will run the translator,
but only recompile those files that would be affected by the changes.
Also, if you build the translator and then want to build the interpreter
(or vice versa), you should make clean (wmake -f makefile.wat clean).
They take a slightly different combination of files (some files are
in one but not the other, and different routines get deleted, leaving
different file sizes).
Matt
6. Re: OpenWatcom
Matt Lewis wrote:
>
> Jason Gade wrote:
> >
> > Robert Craig wrote:
> > >
> > > Matt Lewis wrote:
> > > > I committed some changes to the Euphoria svn repository to fix the
> > > > source
> > > > for OpenWatcom. There's also a makefile (makefile.wat) for building
> > > > it using OpenWatcom.
> > >
> > > Good. I can compile with OpenWatcom, but
> > > I still normally use Watcom 10.6 because
> > > of the "pop up to full screen" issue in DOS.
> > > I'm glad there's a developer using OpenWatcom.
> > > I see you added "EOW".
> > >
> >
> > Sorry if the last message shows up; I meant to quote.
> >
> > What's EOW? That has been bugging me all day.
> >
>
> If you've looked at the source, you've probably noticed several macros
> that identify the platform and compiler being used. There are a couple
> of places that need to be different from Watcom 10.6 vs Open Watcom 1.5
> (be_callc.c and be_runtime.c). I added a new macro (EOW) to specify
> that the OpenWatcom compiler is being used. The convention that Rob has
> used is to prefix any of his macros with an 'E', so I used that, too.
>
> The makefile is handy, because it only compiles the files that have been
> changed. If you make changes to the front end, you may need to change the
> makefile. The translator will break up large files, and changes (additions,
> deletions, etc) may produce different files. Basically, if any of the
> euphoria source files for the front end change, it will run the translator,
> but only recompile those files that would be affected by the changes.
>
> Also, if you build the translator and then want to build the interpreter
> (or vice versa), you should make clean (wmake -f makefile.wat clean).
> They take a slightly different combination of files (some files are
> in one but not the other, and different routines get deleted, leaving
> different file sizes).
>
> Matt
Thanks, Matt. No, I haven't actually looked at the sources yet. I am not sure
when I will, but I am interested in making changes that would support the Digital
Mars and the MingW compilers.
However large projects are not my forte, so I'm not sure if or when that will
happen.
--
"Any programming problem can be solved by adding a level of indirection."
--anonymous
"Any performance problem can be solved by removing a level of indirection."
--M. Haertel
"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare
j.
7. OpenWatcom
- Posted by euman at bellsouth.net
May 16, 2002
OpenWatcom is now a reality......
ftp://ftp.openwatcom.org/watcom/openwatcom/
27.4 meg .zip D/L, 18,000 source code files totalling nearly 78MB
WOW, a *LOT* of code so everyone get busy writting a Euphoria
compiler OK...ok, just kidding about that part.
Euman
8. Re: OpenWatcom
- Posted by rforno at tutopia.com
May 16, 2002
I'll try Open Watcom for EU2C after I finish downloading it 
. But a
question comes to my mind: why is it so huge? Compare it with the xs
compiler from Romania, that not only is C compatible (not totally) but
allows to define other languages. There is an alpha release for Windows,
compatible with C++, they say, which I just finished downloading. Their
size is between 1 and 2 Mb. You can get them free from:
http://web.cs.pub.ro/~vycxs/xs
I'd like to hear comments on the subject, since I am short of time to try
them.
----- Original Message -----
From: <euman at bellsouth.net>
To: "EUforum" <EUforum at topica.com>
Subject: OpenWatcom
>
> OpenWatcom is now a reality......
> ftp://ftp.openwatcom.org/watcom/openwatcom/
>
> 27.4 meg .zip D/L, 18,000 source code files totalling nearly 78MB
> WOW, a *LOT* of code so everyone get busy writting a Euphoria
> compiler OK...ok, just kidding about that part.
>
> Euman
>
>
>
>
