- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Using the command
OPEN(UNIT = 9, FILE = FILLIN, RECL = 200, FORM = 'FORMATTED', &
ACCESS = 'DIRECT')
I get a file with CR/LF ending the 200 byte records in Release whereas the file has only CR (or maybe just LF) in Debug. Why?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Compare the project options - there is probably one you have set in one configuration and not the other. I would look specifically at /fpscomp.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Compare the project options - there is probably one you have set in one configuration and not the other. I would look specifically at /fpscomp.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am noting the Release executable has the options
/fpscomp:ioformat /fpscomp:ldio_spacing /fpscomp:general
whereas the Debug executable does not. Are these the cause (or the savior)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yep. It's /fpscomp:general that is causing the difference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That did the trick, putting /fpscomp:general as an "AdditionalOption" in the debug executable.
Thank you.
Most of these options are legacy, as in were implemented before I saw the code 8 years ago. Where might the documentation on such things be?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same place as the other options - in the compiler documentation. Look in the index under /fpscomp.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page