Re: Elemental constraints on pointer components

Sorry for not being clearer in my question. I could have saved
some bandwidth if I hadn't been so terse. Richard correctly
understood my question. What I wanted was a deep copy of data
pointer components (hence the need for a defined assignment),
but 'shallow' copy of procedure pointers (as if there could
be anything else) and was misled by the NAG compiler into
believing that there was no distinction between the two types
of pointers (and hence the assignment couldn't be elemental).
I'm relieved to learn that this isn't the case.

-Neil
.

Relevant Pages

  • Re: why cannot assign to function call
    ... as in Python, Java, REALbasic, .NET, etc. ... Pointers are passed and assigned by value, ... If you simply use the name, you get by-value semantics. ... Python's assignment semantics, and further appear ...
    (comp.lang.python)
  • Re: Destructor that implies another destructor call (using new/delete)
    ... the assignment you have: ... First an array of pointers to X is created on the heap, ... For the 'explicit' keyword I used in the constructor overload, ... declared in A as a singular pointer vs your correct declaration: ...
    (microsoft.public.vc.language)
  • Re: Destructor that implies another destructor call (using new/delete)
    ... the assignment you have: ... This didn't work for me directly, instead I tried adding an explicit ... First an array of pointers to X is created on the heap, then the pointers are assigned in the loop. ... For the 'explicit' keyword I used in the constructor overload, it helps in avoiding subtle bugs due to *implicit* conversions. ...
    (microsoft.public.vc.language)
  • Re: Cobol work?
    ... > Rick, both your issues involve misuse of features, not features that are ... than Pascal pointers, or Cobol pointers for that matter. ... > assignment operator was insane. ... notation to indicate what we would call today "assignment". ...
    (comp.lang.cobol)
  • Re: why one array continues to grow after repeated call
    ... I'm not intentionally trying to be obstinate, it just seems there is no practical impact to what happens, or to my thinking process as a programmer, to not consider a= 3 an assignment. ... I'm assuming the same is true for any variable in Ruby, ... char *a; ... And it's the same in C for pointers, ...
    (comp.lang.ruby)
Loading