deftofd wrong formatting

[Nikita_Tropin]

Hello,

I had a fortran project in Visual Studio 2005 then I've installed Visual Studio 2008 and convert the project. Then after editing visual interface in Script1.rc I've found that resource.fd isn't renewed. The advice was to add resource.h to project and add custom pre-build step deftofd resource.h resource.fd.

After doing it in my resource.fd I have strings like these:

character(len=6), parameter :: IMAGE_FILE_MACHINE_I386 = ("0x014c"&
&)
integer, parameter :: TAPE_DRIVE_ERASE_SHORT = z'00000010'
integer, parameter :: PRODUCT_STORAGE_EXPRESS_SERVER = z'00000014'&
&
integer, parameter :: PRODUCT_WEB_SERVER = z'00000011'

And these marked strings (when continuation symbol is on next string alone) cause errors:

error #5153: Illegal continuation. No valid non_commentary source following &.

error #5082: Syntax error, found IDENTIFIER 'INTEGER' when expecting one of: * ) :: , ; + . - (/ [ : ] /) ' ** / // > .LT. ...

I believe that is because deftofd.exe formats strings with certain length in a wrong way.

I have Intel Fortran 11.1.

[Steven_L_Intel1]

Would you please attach the resource.h that triggers this?

[nvaneck]

I've not had that problem but I have to run that step separately every time I have to add another control. Existing controls always update ok, though. I'm using release 10, so maybe that part of the problem is overcome by release 11. Didn't have the problem in earlier releases.

[Steven_L_Intel1]

nvaneck, it may be that you did not correctly add the custom build step to run deftofd.

[Nikita_Tropin]

Steve,

I've cutted one of the strings that causes the error.

Attached are 1.h and 1.fd that I've made by command "deftofd.exe 1.h 1.fd"

[nvaneck]

Could be; it used to work. I thought I followed the directions with several attempts, but I have the work around anyway.

[Steven_L_Intel1]

Thanks, Nikita. I can reproduce this and will report it to the developers. The issue ID is DPD200149906.

[Steven_L_Intel1]

I expect the fix for this to be included in Update 6, scheduled for April.