Re: Using "return" values or "out" arguments (fwd)

Hi, all.  As many as all may be.

I'm forwarding this list-relevant message from Duke to the list.  And
I just bounced my direct message to him to the list.

I'm about to take over from Fadi as the Sather maintainer.  So maybe I
can express a preference in this connection.  The list doesn't have a
lot of traffic, and I think it would be better for discussions of
Sather to be public, go through the list.

If you don't want to send two messages, one direct and one to the
list, please give the list preference.

I don't know why the list or my mail client or whatever has been set
up to do both.  Will look into it some time.

-- 
Michael Talbot-Wilson

---------- Forwarded message ----------
Date: Thu, 8 Mar 2012 05:07:58 -0700
From: Duke Normandin <[email protected]>
To: Sather User <[email protected]>
Subject: Re: Using "return" values or "out" arguments

On Thu, 8 Mar 2012 17:42:40 +1030 (CST)
Sather User <[email protected]> wrote:


[snip]

> But maybe I was wrong all along.  Here is a routine (named create)
> with a return value that seems to not require use of the return
> value. I want debug messages to be in create expressions like
> #OUT.

[snip]

> That works as unexpected.  It prints "yes, debugging" without
> protest, although DDD::create:SAME has a return value that isn't
> assigned.  Is this right, or am I missing something?  Is the
> return value used, or not?

I'm curious about:
- the answer to your issue
- the indication we'll receive of the existence and extent of a
Sather community. :) I'd love to see other Sather guru hackers come
out of the woodwork and rally around your finding!! :D

-- 
Duke Normandin
Turner Valley, Alberta, Canada