comp.lang.idl-pvwave archive: archive » Re: Error when using !NULL as a property value. Bug or feature?

Home » Public Forums » archive » Re: Error when using !NULL as a property value. Bug or feature?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Error when using !NULL as a property value. Bug or feature? [message #76438]

Thu, 02 June 2011 09:12

Michael Galloy
Messages: 1114
Registered: April 2006

Senior Member

On 6/2/11 9:56 AM, Jason Ferrara wrote:
> pro proptest::GetProperty, something=s, empty=e
> s = [1,2,3]
> e = []
> end
>
> PRO proptest__define
> struct={proptest, INHERITS IDL_Object}
> END

Yes, e seems to be loosing its special !null status and becoming just a
normal undefined variable somewhere along the line:

pro proptest::GetProperty, something=s, empty=e
s = [1,2,3]
e = !null
help, e
end

And then:

[334]> p = proptest()
[335]> help, p.empty
E UNDEFINED = !NULL
<Expression> UNDEFINED = <Undefined>

It is OK to return normal undefined variables (like above), but not to
use them in an assignment.

Mike
--
Michael Galloy
www.michaelgalloy.com
Modern IDL, A Guide to Learning IDL: http://modernidl.idldev.com
Research Mathematician
Tech-X Corporation

Report message to a moderator

[Message index]

		Re: Error when using !NULL as a property value. Bug or feature? By: Michael Galloy on Thu, 02 June 2011 09:12
		Re: Error when using !NULL as a property value. Bug or feature? By: chris_torrence@NOSPAM on Fri, 10 June 2011 15:47

Previous Topic:	Re: New Object Method Invocation Syntax Brokenness
Next Topic:	dynamic linking on Mac

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 15:20:30 PDT 2025

Total time taken to generate the page: 0.00513 seconds