[Bug fortran/37605] Remarks on user manual for Gfortran
--- Comment #10 from dfranke at gcc dot gnu dot org 2009-04-10 21:03 --- Closing as this seems to be completed. Please reopen if there's an issue left. Thanks for the reports! -- dfranke at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37605
[Bug fortran/37605] Remarks on user manual for Gfortran
--- Comment #9 from dfranke at gcc dot gnu dot org 2009-01-04 00:29 --- Anything left here? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37605
[Bug fortran/37605] Remarks on user manual for Gfortran
--- Comment #8 from domob at gcc dot gnu dot org 2008-12-21 18:46 --- Subject: Bug 37605 Author: domob Date: Sun Dec 21 18:45:17 2008 New Revision: 142866 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=142866 Log: 2008-12-21 Arjen Markus arjen.mar...@wldelft.nl Daniel Kraft d...@domob.eu PR fortran/37605 * gfortran.texi: Fixed some typos and some minor style improvements. * intrinsic.texi: Some clarifications and typo-fixes. * invoke.texi: Better documenation of the behaviour of the -fdefault-*-8 options and some other fixes. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/gfortran.texi trunk/gcc/fortran/intrinsic.texi trunk/gcc/fortran/invoke.texi -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37605
[Bug fortran/37605] Remarks on user manual for Gfortran
--- Comment #6 from domob at gcc dot gnu dot org 2008-12-10 08:44 --- I did post it to the mailing list some time ago and there was a little discussion, IIRC, but no definite review or OK for it. But I can re-post it (or we welcome your opinions), of course. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37605
[Bug fortran/37605] Remarks on user manual for Gfortran
--- Comment #7 from dfranke at gcc dot gnu dot org 2008-12-10 10:01 --- But I can re-post it (or we welcome your opinions), of course. Please repost. I haven't looked into it in detail yet. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37605
[Bug fortran/37605] Remarks on user manual for Gfortran
--- Comment #5 from dfranke at gcc dot gnu dot org 2008-12-09 22:17 --- Any specific reason why this wasn't applied yet? -- dfranke at gcc dot gnu dot org changed: What|Removed |Added CC||dfranke at gcc dot gnu dot ||org Keywords||documentation, patch http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37605
[Bug fortran/37605] Remarks on user manual for Gfortran
--- Comment #4 from domob at gcc dot gnu dot org 2008-10-04 06:45 --- Created an attachment (id=16461) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16461action=view) Patch addressing most of the specific remarks This patch (posted to the list some time ago) addresses most of the specific remarks; I'm not sure what we should do about it, but in my opinion at least most of them are really improvements nice to have. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37605
[Bug fortran/37605] Remarks on user manual for Gfortran
--- Comment #1 from domob at gcc dot gnu dot org 2008-09-21 10:27 --- Hi, thanks for having a look at the manual! This is surely greatly appreciated! (In reply to comment #0) General remarks --- 1. Section on distributing programs is missing: What is needed if you have created a product to distribute it to customers? (Either with or without sources) 2. Section on floating-point issues is missing: How do the compile options influence the floating-point behaviour? What is the treatment of special values such as Inf and Nan? What happens with atan2(0,0)? 3. POSIX-type extensions in the language reference: No particular information is given how the various functions (SYMLNK for instance or STAT) work (or do not work) on a non-POSIX system like MS Windows. All of those sound good to me (haven't read through your specific remarks, but those are most probably 'obvious' and ok as well). I'll confirm this PR. I'm sure both a patch fixing the missing/superfluous words (or a set of patches to split it up to managable sizes) and patches to add the new documentation mentioned above will be very welcomed. If you need assistance in figuring out the information needed, just ask at [EMAIL PROTECTED] and someone will hopefully help :) -- domob at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2008-09-21 10:27:21 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37605
[Bug fortran/37605] Remarks on user manual for Gfortran
--- Comment #2 from domob at gcc dot gnu dot org 2008-09-21 10:31 --- Just one more comment: Thanks for the great list of typos and suggestions; if you want and need help, I can volunteer to fix some of them if I find some time to do so, as this should be trivially possible now with your preparation :) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37605
[Bug fortran/37605] Remarks on user manual for Gfortran
--- Comment #3 from arjen dot markus at wldelft dot nl 2008-09-21 10:51 --- Subject: Re: Remarks on user manual for Gfortran --- Comment #2 from domob at gcc dot gnu dot org 2008-09-21 10:31 --- Just one more comment: Thanks for the great list of typos and suggestions; if you want and need help, I can volunteer to fix some of them if I find some time to do so, as this should be trivially possible now with your preparation :) Hi, if you can do that, that would be great - I am quite new to this process and submitting such remarks is much easier than providing the actual patch :). I can try and supply text describing what happens on the Windows platform (that would be merely a matter of writing a small program and checking the effects). Things regarding floating-point and distributing an application are slightly tougher, as they probably involve the properties of the various platforms. Regards, Arjen -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37605
