comp.lang.idl-pvwave archive: archive » When Ptr

Home » Public Forums » archive » When Ptr_New doesn't work

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

When Ptr_New doesn't work [message #28954]

Tue, 22 January 2002 03:42

badenes
Messages: 5
Registered: January 2002

Junior Member

I have the following problem:

rCoefficients=PtrArr(nElems)
FOR i=0, nElems-1 DO BEGIN
rCoefficients[i]=Ptr_New(PtrArr(elems[i]))
ENDFOR

since elems is a vector of integers, each element i of
rCoefficients is a pointer to an array of elems[i] pointers.
But, for some reason,

((*rCoefficients[j])[k]) = Ptr_New(FltArr(2), /NO_COPY)

doesn't work. k and j are within the allowed range, of course, and
((*rCoefficients[j])[k]) is a null pointer, as expected from the
initialization above. Ptr_New is supposed to allocate memory for the
specified pointer to store an array of 2 floats, but I get the message

Expression must be named variable in this context: <POINTER
(<NullPointer>)>.

I must be doing something wrong. Can you help?

Thanks,
Carles

Report message to a moderator

[Message index]

		When Ptr_New doesn't work By: badenes on Tue, 22 January 2002 03:42
		Re: When Ptr_New doesn't work By: John-David T. Smith on Wed, 23 January 2002 11:13
		Re: When Ptr_New doesn't work By: Pavel A. Romashkin on Wed, 23 January 2002 10:07

Previous Topic:	Re: When Ptr_New doesn't work
Next Topic:	Re: Does anybody know an 'undocumented IDL feature' that does this

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Oct 09 16:06:40 PDT 2025

Total time taken to generate the page: 0.88061 seconds