Re: Major Bug in Interpreter [Attn: Robert Craig]
- Posted by Patrick Barnes <mrtrick at gmail.com> Feb 15, 2005
- 469 views
On Tue, 15 Feb 2005 13:58:41 -0800, Georg Wrede <guest at rapideuphoria.com> wrote: > }}} <eucode> > tmp = function_call_with_side_effects(i+1) > stack[ib][i] = tmp > </eucode> {{{ > > is actually "for free"!! Very nice. > > There's also the issue of writing non-ambiguous code. Just like > putting a few extra parentheses in complicated logical expressions, > splitting lines like the above just serve the reader of the code. > > They make a huge service to all by making it explicit what order > of evaluation we want. Besides, the next guy who has to take over > your code doesn't have to know esoteria and arcana about Euphoria > enough to guess himself what the order of evaluation would be on > a single line. I agree, code should be written unambiguously. Rob, it's not possible to stop someone from creating unreadable code, but it would help the Euphoria community if a warning was given for ambiguous things like this - if a variable is modified in the same line as it is referenced. -- MrTrick