Re: [Oorexx-devel] Native API methods with no return value?

2008-07-23 Thread Rick McGuire
If you want to return nothing, then declare the return type as
RexxObjectPtr and return NULLOBJECT.  This will only raise an error if
the method is used in an expression context.  For example,

   say x~'STATE='(1)

Would return raise an error, but

x~state=1

would not.

A VOID return type just didn't work real well with the macro
expansions, so the routines/methods had to have some minimal return
type defined.

One possibility I considered (ok, actually, I just thought it up) is
having a type like NORETURNVALUE that could only be specified as a
return value (not an argument).  You'd still need to have some sort of
return (mapped to an int maybe), but then the runtime would always
force this to be a return-value free situation.  That would allow you
to be more explicit that the method does not really return a value.

Rick

On Wed, Jul 23, 2008 at 1:31 PM, Mark Miesfeld [EMAIL PROTECTED] wrote:
 Hi Rick,

 If you have a method that has no return when using the native API,
 what should you do?  I think return .nil, or even return int 0, but
 wondered if you had something better in mind.

 In particular I wanted to use a method for this:

 ::method state= external LIBRARY oodialog bc_setState

 I'm not sure if there are any consequences of returning something for
 an equals method.

 --
 Mark Miesfeld

 -
 This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
 Build the coolest Linux based applications with Moblin SDK  win great prizes
 Grand prize is a trip for two to an Open Source event anywhere in the world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 Oorexx-devel mailing list
 Oorexx-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/oorexx-devel


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Native API methods with no return value?

2008-07-23 Thread Mark Miesfeld
On Wed, Jul 23, 2008 at 10:39 AM, Rick McGuire [EMAIL PROTECTED] wrote:

 If you want to return nothing, then declare the return type as
 RexxObjectPtr and return NULLOBJECT.

I think that works well.  Your idea of having a type like
NORETURNVALUE is good, and I was wondering if you had something like
that when I asked the question.  But, I think returning NULLOBJECT
would be enough of a signal that the method is not intended to return
anything.

--
Mark Miesfeld

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel