1. v2.5
Well so far, 2.5 is running well.
Robert: It isn't clear so far but can we buy the source code
for the front end only? I don't want the back end source code.
--
Derek Parnell
Melbourne, Australia
2. Re: v2.5
Derek Parnell wrote:
>
> Well so far, 2.5 is running well.
>
> Robert: It isn't clear so far but can we buy the source code
> for the front end only? I don't want the back end source code.
The front end source code (scanner, parser, IL emitter etc.)
is free - Public Domain.
It's in euphoria\source, and it's the same code I am now using
in the front end of ex.exe, exw.exe, exu. The only differences are:
A. I have a secret bit of code for decoding old shrouded programs
B. I have a bit of extra closed-source Euphoria code that
interfaces the Euphoria front-end with my C back-end.
C. euphoria\source has an extra file, execute.e, that acts
as a back-end. I don't use that. I use a faster C back-end.
I have to keep A to myself. You'll get B when
you buy the full Euphoria + C source package
(free upgrade for you - but check the new source license first).
For extra speed, I translate the Euphoria front end files
to C, before linking them with my hand-coded back-end C files.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: v2.5
Robert Craig wrote:
>
> C. euphoria\source has an extra file, execute.e, that acts
> as a back-end. I don't use that. I use a faster C back-end.
>
This 'execute.e' will make writing a Euphoria scripting language
very possible. All one has to do is create the IL code for the script
and run it. Very nice.
So who will be first with a usable 'evaluate()' routine 
--
Derek Parnell
Melbourne, Australia
4. Re: v2.5
Derek Parnell wrote:
> Robert Craig wrote:
> > C. euphoria\source has an extra file, execute.e, that acts
> > as a back-end. I don't use that. I use a faster C back-end.
> This 'execute.e' will make writing a Euphoria scripting language
> very possible. All one has to do is create the IL code for the script
> and run it. Very nice.
>
> So who will be first with a usable 'evaluate()' routine
Is this the next contest? :)
-=ck
"Programming in a state of EUPHORIA."
http://www.cklester.com/euphoria/
5. Re: v2.5
On Tue, 16 Nov 2004 20:21:53 -0800, cklester <guest at rapideuphoria.com> wrote:
>
> posted by: cklester <cklester at yahoo.com>
>
> Derek Parnell wrote:
> > Robert Craig wrote:
> > > C. euphoria\source has an extra file, execute.e, that acts
> > > as a back-end. I don't use that. I use a faster C back-end.
> > This 'execute.e' will make writing a Euphoria scripting language
> > very possible. All one has to do is create the IL code for the script
> > and run it. Very nice.
> >
> > So who will be first with a usable 'evaluate()' routine
>
> Is this the next contest? :)
Interesting, but no. Maybe next month?
I'm working on the framework for the next contest, the rules will be
made available in the next couple of days, unless Derek feels that
would let the wind out of his sails...
--
MrTrick
6. Re: v2.5
Derek Parnell wrote:
> So who will be first with a usable 'evaluate()' routine
who will be first that will write windows debugger? (is it allowed to share it?)
7. Re: v2.5
Tone Škoda wrote:
>
> Derek Parnell wrote:
>
> > So who will be first with a usable 'evaluate()' routine
>
>
> who will be first that will write windows debugger? (is it allowed to share
> it?)
I've been assuming that someone will create a spiffy Windows debugger
for the PD source. Of course it can be shared if the author wants to.
There are probably a lot of interesting debugging tools that
could be created without too much trouble. Not to mention
source code analysis tools, symbol table dumps, etc.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
8. Re: v2.5
On 16 Nov 2004, at 19:33, Derek Parnell wrote:
>
>
> posted by: Derek Parnell <ddparnell at bigpond.com>
>
> Robert Craig wrote:
>
> >
> > C. euphoria\source has an extra file, execute.e, that acts
> > as a back-end. I don't use that. I use a faster C back-end.
> >
>
> This 'execute.e' will make writing a Euphoria scripting language
> very possible. All one has to do is create the IL code for the script
> and run it. Very nice.
>
> So who will be first with a usable 'evaluate()' routine
Not me, i am going to be in jail for defending myself from a vicious adult male
rottwiler attack dog attacking me on my own property. If i am still alive to
goto jail.
Kat
9. v2.5
I cannot run ed.ex with exwc, the executeable dies with a "tried to
get memory from XXXXX" message.
Using w2000...
--
MrTrick
-------------------------------------------------------------------------------------
magnae clunes mihi placent, nec possum de hac re mentiri.
10. Re: v2.5
Derek Parnell wrote:
>
> This 'execute.e' will make writing a Euphoria scripting language
> very possible. All one has to do is create the IL code for the script
> and run it. Very nice.
>
> So who will be first with a usable 'evaluate()' routine
>
I think the key to this may be a preprocessor that creates routines
for access to variables in the main program.
Matt Lewis
11. Re: v2.5
Robert Craig wrote:
>
> Tone Škoda wrote:
> >
> > Derek Parnell wrote:
> >
> > > So who will be first with a usable 'evaluate()' routine
> >
> >
> > who will be first that will write windows debugger? (is it allowed to share
> > it?)
>
> I've been assuming that someone will create a spiffy Windows debugger
> for the PD source. Of course it can be shared if the author wants to.
> There are probably a lot of interesting debugging tools that
> could be created without too much trouble. Not to mention
> source code analysis tools, symbol table dumps, etc.
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
>
A nice Windows debugger would be awasome. :)
12. Re: v2.5
- Posted by jiri babor <jbabor at paradise.net.nz>
Nov 17, 2004
-
Last edited Nov 18, 2004
It looks really nice, Rob. You have, finally, found a better way to milk your
little cash goat: the 'complete' edition is gone! But your coding style is still
atrocious, ask Derek.
jiri
13. Re: v2.5
- Posted by Robert Craig <rds at RapidEuphoria.com>
Nov 17, 2004
-
Last edited Nov 18, 2004
Patrick Barnes wrote:
> I cannot run ed.ex with exwc, the executeable dies with a "tried to
> get memory from XXXXX" message.
> Using w2000...
I wonder if you can try exw.exe, and ex.exe, and report
if the result is different.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
14. Re: v2.5
- Posted by Patrick Barnes <mrtrick at gmail.com>
Nov 17, 2004
-
Last edited Nov 18, 2004
It works on ex.exe, haven't tried with exw.exe, will do so when I get home.
On Wed, 17 Nov 2004 13:05:17 -0800, Robert Craig
<guest at rapideuphoria.com> wrote:
>
> posted by: Robert Craig <rds at RapidEuphoria.com>
>
> Patrick Barnes wrote:
> > I cannot run ed.ex with exwc, the executeable dies with a "tried to
> > get memory from XXXXX" message.
> > Using w2000...
>
> I wonder if you can try exw.exe, and ex.exe, and report
> if the result is different.
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> http://www.RapidEuphoria.com
>
>
>
>
--
MrTrick
