Use of the ENUM keyword

I want to use the ENUM keyword in manner described under '.NET enumerated types' in FTN95 help, but when I use syntax shown there (see below), I get a syntax error on the ENUM statement. I cannot find any other reference to the ENUM keyword in any other section of the help. The example below, given in help, also generates a syntax error when compiled. Any help would be appreciated.

CHARACTER(LEN=60),PARAMETER::CONVENTION='System.Runtime.InteropServices.CallingConvention' ENUM(CONVENTION)::MY_CONVENTION

Also getting syntax error with this code despite copying it exactly from the help. I was trying with my own enums to start with but since that was failing, I tried the example.

Any comments?

We are looking into this.

This syntax doesn't work. The compiler has some code to handle the syntax but none of it is hooked up and has never worked.

Quoted from silverfrost This syntax doesn't work. The compiler has some code to handle the syntax but none of it is hooked up and has never worked.

Can you please let us know what you are going to do about this?

I plan to find out how much work would be required to implement this Fortran 2003 feature. I am hopeful that it will not be too much and that we will be able to make ENUM work in the way that is outlined in the help file. Realistically this work may not be completed before the next release.

Having said this, my own view is that ENUM is not a particularly significant feature. Even when coding in C++ I do not necessarily use enum when it would be natural to do so.

They make much better readable code and are nice to work with, for example using the IntelliSense things in c#.

I don't know if this is helpful in this case, but for interfacing (with fortran, though I'd avoid that) you may use casts in order to pass a basic type instead of an enum. Like define the enum as 'enum direction : int ' and use (int)dir (where dir is of type direction) for passing the value. Doesn't look nice and introduces dependencies between the two code bases, but may be useful in some cases.

Quoted from PaulLaidler Having said this, my own view is that ENUM is not a particularly significant feature.

A great deal of the .NET framework uses enums. In order to access this from FTN95 without enum support, I would have to look up the integer value every time I wanted to use it!