Well, it is Friday afternoon and I fell depressed and tied to do any
work useful. So it may be the time to make fool of myself again. :-)
_What_bugs_me_ is that after so many messages about "\n", it is unclear
to me where exactly the experts agree or disagree.
IMHO, the problem could be solved by adding a C_ESCAPE() function in the
ISO_C_BINDING intrinsic module. C_ESCAPE("\n") would be the same as
whatever the value defined by _a_ C compiler on that same OS targeted
for C Interoperability. Isn't there already a C_NULL_CHAR in the draft
standard for similar situations?
Cheers,
Jing
--
________________________________ _-__-_-_ _-___---
Jing Guo, [log in to unmask], (301)614-6172(o), (301)614-6297(fx)
Data Assimilation Office, Code 910.3, NASA/GSFC, Greenbelt, MD 20771
|