OpenEuphoria

Re: pbr vs multiple returns

• Posted by Matt Lewis <matthewwalkerlewis at gmail.com> Jan 11, 2007
• 541 views

Chris Bensler wrote:
> 
> Pete Lomax wrote:
> > 
> > Chris Bensler wrote:
> > 
> > My apologies for the recent (part 4) post.
> 
> No offense taken. I'm just very frustrated with trying to justify myself to
> everyone.
> 
> Personally I'd like to know where Euphoria wants to go, so I can either start
> making it happen or get on with my own things instead. This limbo is good for
> nobody.
> 
> Everybody has a wishlist and it's always religious war. We should not be
> trying
> to dictate what should be in Eu, we should be listening to what Eu needs. As
> I said before, maybe Eu is perfect for what it's supposed to be already and
> we are all bashing heads for nothing.
> 
> We need to recognize the separation of varying opinions and perspectives on
> priority and find a comprimise before we can begin to determine what is
> practical
> to implement.

I thought that's what we were doing.  Seriously, though, on one hand, I
understand (and to an extent, share) your frustration--dammit, why can't
they all just see that I'm right?!? :)

> > }}}
<eucode>
> >   {x,y}@="chris"
> > </eucode>
{{{

> > sets both x and y to "chris" rather than x to 'c' and y to 'h'. Same deal of
> > course with {x,y} at =get_name().

> 
> What's wrong with repeat() ?

I think what Pete is talking about is kinda the complement (reverse? 
whatever) of repeat().  He's taking one thing and assigning it to several
things with a single statement.  It's just syntactic sugar, compressing
things into a single statement.  Personally, I don't see that it adds
very much, and would vote to keep it out at this point.

Matt