[Patch, fortran] Document libgfortran thread-safety

[Janne Blomqvist]

On Mon, Feb 7, 2011 at 21:09, Ralf Wildenhues <Ralf.Wildenhues@gmx.de> wrote:
> * Janne Blomqvist wrote on Mon, Feb 07, 2011 at 08:03:17PM CET:
>> On Sun, Feb 6, 2011 at 23:45, Ralf Wildenhues <Ralf.Wildenhues@gmx.de> wrote:
>> > * Janne Blomqvist wrote on Sat, Feb 05, 2011 at 10:44:48PM CET:
>> >> --- a/gcc/fortran/gfortran.texi
>> >> +++ b/gcc/fortran/gfortran.texi
>> >> @@ -1157,6 +1157,36 @@ representation of @code{LOGICAL} variables in GNU Fortran is identical
>> >>  to C99 _Bool, except for a possible difference in storage size
>> >>  depending on the kind.
>> >>
>> >> +
>> >> +@node Thread-safety of the runtime library
>> >> +@section Thread-safety of the runtime library
>> >> +@cindex thread-safety, threads
>> >> +
>> >> +GNU Fortran can be used in programs with multiple threads, e.g. by
>> >
>> > e.g.@: by
>>
>> I don't understand what you mean by that.
>
> In the PDF output, TeX adds more spacing after an end-of-sentence
> period.  After an abbreviation however, you don't want that larger
> space.  Writing e.g.@: gets TeX to only add normal spacing.
> See 'info texinfo "Not Ending a Sentence"'.
>
> It's a very minor nit.  But since we fixed all instances of 'e.g.'
> and 'i.e.' for the 4.5 release, it would be nice to not regress.

Ok, fixed. I also took the liberty of fixing a few other spurious
()'s, and one bug (errno is a variable, not a function). Committed as
obvious

Sending        fortran/gfortran.texi
Sending        fortran/intrinsic.texi
Transmitting file data ..
Committed revision 169893.

(I didn't include a ChangeLog entry as IMHO it goes under the previous one).



-- 
Janne Blomqvist