Hello,
>It's all OK so long as in any scoping unit all specific interfaces within
>the union of generics with a particular <generic-spec> that are accessible
>at that point satisfy the restrictions on generic definitions (14.1.2.3 in
>the F95 standard).
>
This is what I thought but Lahey was telling me otherwise. It seems I
have uncovered some very peculiar bug, as NAG and Intel both do as you
say they should.
In my program I use 4 modules which all add to a given generic interface:
USE MakeArrayDescriptorWrapper_Position_2D
USE MakeArrayDescriptorWrapper_Velocity_2D
USE MakeArrayDescriptorWrapper_Orientation_2D
USE MakeArrayDescriptorWrapper_AngularVelocity_2D
and it seems like with Lahey only the generic from the first module is
added to the union. So my program fails with different errors depending
on the permutation of the above USE statements. Definitely a bug! But I
cannot reproduce this with the smaller test example Raju sent, so it is
strange...
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
__________________________________
|