You may all have some valid points there with regards to
pointers initially in an "undefined" state for debugging,
more in line with other variables, etc etc.
BUT that doesn't solve the main problem, viz. one cannot test
a pointer in an undefined state via ASSOCIATED. If a pointer
is undefined, and one cannot always prevent this from happening,
and I test such a pointer the code crashes under a number of
compilers (unless some compiler switches are available but that
is usually neither portable nor attractive).
Cheers,
WWS
-----------------------------------------------------------------------
| Werner W Schulz |
| Dept of Chemistry email: [log in to unmask] |
| University of Cambridge Phone: (+44) (0)1223 336 502 |
| Lensfield Road Secretary: 1223 336 338 |
| Cambridge CB2 1EW Fax: 1223 336 536 |
| United Kingdom WWW: |
-----------------------------------------------------------------------
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|