Iso Varying String Native Support

[Intel_C_Intel]

When are you planning to incorporate the 'iso varying string' and other F2003 facilities to IFC? Maybe in the next major version :-). I would like to stop receiving non-standard F95 warnings and start checking for standard F2003 compliant code. Thanks,

Bernhard Enders.

[Intel_C_Intel]

Where can I find a document describing the already implemented F2003 features of the latest version of IFC? Thanks again.

Bernhard.

[Steven_L_Intel1]

ISO_VARYING_STRING is not part of the actual F2003 standard. You can use one of the reference implementations today if you want - ideally one that uses allocatable components and not pointer components.

The compiler release notes contain an up-to-date list of the F2003 features supported. We will add to this list over time.

[drgfthomas]

The ISO_VARYING_STRING that comes with CVF compiles fine in IVF 9.1 but it generates a run-time error when IVF finds that the integer 'nch' hasn't been initializedwhen referenced in subs get_d_eorand get_u_eor. /Qzero has no effect. This behavior doesn't occur in CVF, ie, no run-time error and get(-ing) varying_string's works as expected. What gives?

[Steven_L_Intel1]

You've found a bug in unitialized variable checking where it does not recognize that a SIZE= specifier in an I/O list is an output item. I'll report it. Turn off uninitialized variable checking if this is a problem.