1. Translator source code
Rob,
did you ever consider selling the translator source code?
Regards,
Juergen
--
Have you read a good program lately?
2. Re: Translator source code
- Posted by Robert Craig <rds at RapidEuphoria.com>
Nov 24, 2004
-
Last edited Nov 25, 2004
Juergen Luethje wrote:
> Rob,
>
> did you ever consider selling the translator source code?
I wouldn't rule it out.
I'll consider it again for the beta release. No promises.
The license would be similar to the Interpreter source.
This would be easier for me than opening up the IL
to the world, and having to document and support
two languages - Euphoria and IL,
both with upward compatibility requirements.
That would let Andy and Derek create fast .exe's
(faster than binding) using their own customized
(and not-to-be-distributed) versions of Euphoria.
However I still need to consider the risks involved in this.
We'll see.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: Translator source code
- Posted by Derek Parnell <ddparnell at bigpond.com>
Nov 24, 2004
-
Last edited Nov 25, 2004
Robert Craig wrote:
>
> Juergen Luethje wrote:
> > Rob,
> >
> > did you ever consider selling the translator source code?
>
> I wouldn't rule it out.
> I'll consider it again for the beta release. No promises.
> The license would be similar to the Interpreter source.
>
> This would be easier for me than opening up the IL
> to the world, and having to document and support
> two languages - Euphoria and IL,
> both with upward compatibility requirements.
>
> That would let Andy and Derek create fast .exe's
> (faster than binding) using their own customized
> (and not-to-be-distributed) versions of Euphoria.
You just don't get it, do you?
*** I don't want to customize the translator (to C)! ***
I want to write a program that will output RDS IL code (unshrouded) that
your binder will then read as input and bind my output with your
backend.exe to form a new .exe file. As you know, I have already paid
with real money to get your 2.5 binder.
Also, anyone else using my program that outputs IL, will also have
to buy your binder to create .exe files. Your backend.exe, when run
as a standalone program, will only read shrouded IL. So people using
my IL generating program still can't directly use your backend.exe
unless they also buy your binder.
Also, my IL generating program may not even use the Euphoria language
as input! I might come up with a source language that is totally
imcompatible with Euphoria.
It's YOUR IL interpreter that I would like to use!
> However I still need to consider the risks involved in this.
> We'll see.
I seriously doubt that.
"There are none so blind than those who refuse to see."
--
Derek Parnell
Melbourne, Australia
