Hello,
I have found a weird bug in one of the compilers I use. Take the piece
of code:
lsd_packing%dhb_box%dhb_event_record =>
lsd_packing%lsd_boundary_record
IF ( .NOT. ASSOCIATED(lsd_packing%dhb_box%dhb_event_record,
lsd_packing%lsd_boundary_record)) THEN
WRITE (OUTPUT_UNIT,*) "HEY!!! Allocating next boundary
record"
...
END IF
The ASSOCIATED test must test true due to the pointer assignment
statement before (note that lsd_packing%lsd_boundary_record is not a
pointer and definitely not null), however, execution gives:
HEY!!! Allocating next boundary record
Waiting for the vendor to fix this bug (which has not appeared before)
and deal with my 5400 lines of code is not worth it. Has anyone seen
such a thing before--any ideas on how to get around it?
Thanks,
Aleksandar
--
__________________________________
Aleksandar Donev
Complex Materials Theory Group (http://cherrypit.princeton.edu/)
Princeton Materials Institute & Program in Applied and Computational Mathematics
@ Princeton University
Address:
419 Bowen Hall, 70 Prospect Avenue
Princeton University
Princeton, NJ 08540-5211
E-mail: [log in to unmask]
WWW: http://atom.princeton.edu/donev
Phone: (609) 258-2775
Fax: (609) 258-6878
__________________________________
|