🚀 go-pugleaf

In article <3vjlmk$8co@caip.rutgers.edu> halasz@caip.rutgers.edu writes:
> In article <3viv5u$bkv@news.cs.tu-berlin.de>, mfx@cs.tu-berlin.de (Markus Freericks) writes
> > .....
> > My proposal: separate the concepts of return-value and return-control-flow,
> > and extend the function syntax to (for example)
> this is _the_ point ....
> 
> > .....
> >   return; /* return from foo with whatever has been assigned to x,y */
> > }
> And "return" no longer is _needed_.

Two words:
	side effects

- what if you _want_ one or all results to be undefined?
- maybe you _want_ to store the result before doing a side effect without
  having to resort to an auxiliary variable, as in

   (int ret) get-locked-int () {
     lock();
     ret = thingie;
     unlock();
     return;
   }

-- Markus