This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Some more fortran safe-ctype & cleanups
- To: neil at daikokuya dot demon dot co dot uk
- Subject: Re: Some more fortran safe-ctype & cleanups
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Date: Wed, 24 Oct 2001 12:00:34 -0400 (EDT)
- Cc: gcc-patches at gcc dot gnu dot org, toon at moene dot indiv dot nluug dot nl
> From: Neil Booth <neil@daikokuya.demon.co.uk>
>
> Kaveh R. Ghazi wrote:-
>
> > One note, there was no direct equivalent to is_hor_space in
> > safe-ctype, so it became ISSPACE && != '\n'.
>
> is_nvspace exists for this case ("is a non-vertical space"). Maybe
> the Fortran front end doesn't handle the CR-LF etc. dilemma properly
> at the moment; I know Java, C, ObjC and C++ do.
>
> is_nvspace() is what cpplib uses.
> Neil.
Yes but as I alluded to in my original posting, its not an exact
match, is_hor_space is true for ' ', '\t', '\v', '\f' and '\r' while
is_nvspace is true for ' ', '\t', '\v', '\f', and '\0'.
The difference is '\r' vs '\0'.
If is_nvspace is "good enough", I'm more than happy to use it instead.
--Kaveh
PS: I'm not sure what you mean by the "CR-LF dilemma".
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Qwest Internet Solutions