forums.silverfrost.com

[wahorger]

After doing a quick look at posts with SCC and 64-bit, I had a comment and a question.

My comment: I have a large amount of "C" code that I need to carry over with my FTN95 code to make the transition to 64-bit. In addition, I have a fair amount of C++ code that I am currently using a gcc compiler (using CodeLite to manage) to compile into DLL's. Right now, the "C" code is compiled with SCC and the resulting OBJ files are placed in a library; easy enough. The C++ code is compiled in 32-bit mode and built into DLL's that are then linked in and provided to my users for run-time. It's not seamless as one might hope, but I'm managing.

There are a few/several forum comments about SCC and its maintenance, specifically that 64-bit modifications to SCC may be accomplished, but it is not guaranteed. I can understand and appreciate that. I'm not asking for a commitment to SCC in any way similar to your commitment to FTN95-64bit.

My question: I still have a need for 64-bit "C"/C++ compiler so: Of the various flavors of C/C++ compilers available, which one is best for interfacing with FTN95 in 64-bit mode? Either DLL's and/or as compiled .OBJ files. Stated another way, which C/C++ compiler do you all use?

[PaulLaidler]

Bill

If you can manage without debug options and you don't need the iostream functions then you might be OK using 64 bit SCC. stdio.h functions are supplied and working.

[wahorger]

Thanks for that, Paul. What about C++? Issues are usually the include files, but I've not had a lot of success in getting complex routines to compile.

[PaulLaidler]

Bill

If you have C++ code that compiles with 32 bit SCC but not with 64 bit SCC then it is worth reporting this by sending us sample code that fails.

64 bit SCC is not fully supported but it is useful to know what does not work and could be fixed time permitting.