OpenEuphoria

Re: Conceptual problem solved by GOTO

• Posted by Jeremy Cowgar <jeremy at cowg?r.co?> Jun 06, 2008
• 751 views

Jason Gade wrote:
> 
> 
> Because the output of the translator is geared for speed; it is not meant to
> be read by or maintained by humans.
> 
> Most code doesn't need to be so highly optimized for the machine. As posted
> at one of your links "that's the compiler's job".
>  
> > Now, I want to take my own domain language used for hospital billings and
> > initial
> > hospital claim auditing and translate that to Euphoria, but can I? Not
> > easily.
> > It's far easier to just translate to C and use gotos. Now, why not just
> > do/keep
> > that? Because it would be far, far easier to use Euphoria as the final
> > language
> > instead of dealing with users changing the domain language, triggering a
> > compilation,
> > swapping in the .so, etc...
> > 

You did not address the rest of my message which was the real reason. As
Euphoria does translating to C, I *need* to do translating to Euphoria. *I* will
never look at that translated code. domain languages is a very common pattern
that saves huge amounts of time in many peoples applications.

Please tell me why I cannot make the same use of goto that C does? Do not say
that C does it for speed, it does not. goto is used for the ease of the
translator.

--
Jeremy Cowgar
http://jeremy.cowgar.com