public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "malitzke at metronets dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/19292] [meta-bug] g77 features lacking in gfortran Date: Sun, 08 Jan 2006 10:41:00 -0000 [thread overview] Message-ID: <20060108104115.31958.qmail@sourceware.org> (raw) In-Reply-To: <bug-19292-8513@http.gcc.gnu.org/bugzilla/> ------- Comment #16 from malitzke at metronets dot com 2006-01-08 10:41 ------- Well I am very glad you people are offended. Imaging how you would feel I some one had called your work a piece of excrement. Excrement (with some minor variation in spelling) comes from Latin and means vernacular M.... in Spain, Portugal, France, Italy and S... in England, Germany, Sweden. At least per Webster excremental is the adjective pertaining to excrement. Pofessor Emerita C. Froese Fischer (Computer Science Vandebilt University) is the principal author of the MCHF Atomic Structure Package. Acoording to Google there are about 139 thousand citations and authorships to her credit. The MCHF package has about 1.5 megabytes of source code. I never met the lady as student, collaborator or otherwise. Calling her work even only by clearly erroneous association excrement is equivalent to calling GCC a piece of excrement. Happy sulking to you all! Now to the coding and standards issues. I stand corrected by Mr Pinski as to the contains issue. I took the statements regarding CONTAINS (page 116)in Fortran 90 Programmning (TMR Ellis et all) literally as just pertaining for fortran modules to get the calling parameters properly to the compiler the way header files do in C. Only much later in the book is the nesting issue broached. However Mr Pinski also jumping a (in may reckoning) to a wrong conclusion in terming my submission the short citation (a fraction of one percent, allowable under my interprtration of Copyright) of Professor Frose Fischer work as being the equivalent the one containing the "excremental" adjective. The 105 label in my submission precedes the first executable statement while the pertinent label in the ealier submission (which never turned up when I searched for various combinations of GTO and fortran) clearly comes after the first executable statement. This makes that "excremental" case a clear violation of 8.1.1.2. To Mr. Kargl I would counsel moderation is the the of the "Imperial" we and perhaps practice some more reading specifications. His interpretation of "is" and "shall be" in relation the 8.1.1.2 clearly shows his lack of experience. Last, but not least, I do not even pretend to be compiler expert, even after having fairly good understanding of the "Dragon Book". At best I am just a tester, regardles of having hacked GCC code since the late 80's to get GCC to work on SCO's 386 Xenix. I got my start with plugboard punched card equipement and worked as real-time assembly programmer. Now, I am just trying (as a retiremnt hobby) to bring code like Professor Froese Fischer's to a wider audience before it is withdrawn from public access in disgust at being belittled. If in the process I can do some further good by testing forthcoming versions of GCC so much the better. Your reactions provide further amusement. As a result of submitting aboout 10 Gigabytes of source code to GCC I have other irons in the fire for the easily offended to get burned. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19292
next prev parent reply other threads:[~2006-01-08 10:41 UTC|newest] Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-19292-8513@http.gcc.gnu.org/bugzilla/> 2005-11-12 23:29 ` fxcoudert at gcc dot gnu dot org 2006-01-07 20:30 ` malitzke at metronets dot com 2006-01-07 21:55 ` kargl at gcc dot gnu dot org 2006-01-07 22:17 ` sgk at troutmask dot apl dot washington dot edu 2006-01-08 0:33 ` malitzke at metronets dot com 2006-01-08 0:51 ` pinskia at gcc dot gnu dot org 2006-01-08 1:58 ` sgk at troutmask dot apl dot washington dot edu 2006-01-08 2:30 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2006-01-08 2:43 ` sgk at troutmask dot apl dot washington dot edu 2006-01-08 10:41 ` malitzke at metronets dot com [this message] 2006-01-08 13:18 ` tobi at gcc dot gnu dot org 2006-01-08 16:37 ` sgk at troutmask dot apl dot washington dot edu 2006-01-08 20:27 ` pault at gcc dot gnu dot org 2006-05-27 19:24 ` sgk at troutmask dot apl dot washington dot edu 2006-05-27 20:24 ` Thomas dot Koenig at online dot de 2006-05-27 20:28 ` sgk at troutmask dot apl dot washington dot edu 2006-07-03 12:14 ` franke dot daniel at gmail dot com 2006-07-03 12:58 ` fxcoudert at gcc dot gnu dot org 2006-07-03 16:41 ` jvdelisle at gcc dot gnu dot org 2006-07-03 17:17 ` sgk at troutmask dot apl dot washington dot edu 2006-07-26 12:07 ` fxcoudert at gcc dot gnu dot org 2006-10-02 9:41 ` fxcoudert at gcc dot gnu dot org 2006-12-17 18:21 ` pertusus at free dot fr 2006-12-18 21:39 ` pertusus at free dot fr 2007-08-14 23:22 ` fxcoudert at gcc dot gnu dot org 2007-08-16 12:10 ` fxcoudert at gcc dot gnu dot org 2005-01-06 14:39 [Bug fortran/19292] New: [metabug] " tobi at gcc dot gnu dot org 2005-01-20 10:47 ` [Bug fortran/19292] [meta-bug] " Thomas dot Koenig at online dot de 2005-01-22 22:33 ` pbrook at gcc dot gnu dot org 2005-01-23 0:25 ` dje at gcc dot gnu dot org 2005-01-23 22:38 ` pbrook at gcc dot gnu dot org 2005-01-29 15:39 ` pinskia at gcc dot gnu dot org 2005-02-19 12:59 ` wilson at gcc dot gnu dot org 2005-02-20 22:21 ` kargl at gcc dot gnu dot org 2005-02-22 13:07 ` pinskia at gcc dot gnu dot org 2005-02-24 14:32 ` rth at gcc dot gnu dot org 2005-03-11 14:17 ` pinskia at gcc dot gnu dot org 2005-03-13 19:10 ` tobi at gcc dot gnu dot org 2005-03-13 19:29 ` tobi at gcc dot gnu dot org 2005-03-14 20:17 ` tobi at gcc dot gnu dot org 2005-03-16 0:19 ` fengwang at gcc dot gnu dot org 2005-03-16 14:32 ` tobi at gcc dot gnu dot org 2005-03-17 2:14 ` pinskia at gcc dot gnu dot org 2005-03-22 22:17 ` fxcoudert at gcc dot gnu dot org 2005-03-22 23:19 ` tobi at gcc dot gnu dot org 2005-03-25 7:07 ` fxcoudert at gcc dot gnu dot org 2005-03-25 13:37 ` fxcoudert at gcc dot gnu dot org 2005-03-26 17:44 ` pinskia at gcc dot gnu dot org 2005-04-03 8:10 ` fxcoudert at gcc dot gnu dot org 2005-04-06 9:54 ` fxcoudert at gcc dot gnu dot org 2005-04-08 11:12 ` fxcoudert at gcc dot gnu dot org 2005-04-20 1:10 ` milan at cmm dot ki dot si 2005-04-20 1:15 ` pinskia at gcc dot gnu dot org 2005-04-23 16:11 ` pault at gcc dot gnu dot org 2005-04-23 16:14 ` pault at gcc dot gnu dot org 2005-04-23 16:15 ` pault at gcc dot gnu dot org 2005-04-23 16:18 ` pault at gcc dot gnu dot org 2005-04-24 14:01 ` tobi at gcc dot gnu dot org 2005-04-30 17:53 ` pinskia at gcc dot gnu dot org 2005-05-03 7:05 ` tkoenig at gcc dot gnu dot org 2005-05-03 19:47 ` tkoenig at gcc dot gnu dot org 2005-05-03 19:50 ` tkoenig at gcc dot gnu dot org 2005-05-03 19:52 ` tkoenig at gcc dot gnu dot org 2005-05-05 23:26 ` pinskia at gcc dot gnu dot org 2005-05-11 11:18 ` pinskia at gcc dot gnu dot org 2005-05-15 3:25 ` pinskia at gcc dot gnu dot org 2005-05-31 17:01 ` ebotcazou at gcc dot gnu dot org 2005-06-16 22:29 ` fxcoudert at gcc dot gnu dot org 2005-06-16 23:04 ` fxcoudert at gcc dot gnu dot org 2005-06-17 16:25 ` fxcoudert at gcc dot gnu dot org 2005-07-01 22:11 ` pinskia at gcc dot gnu dot org 2005-07-07 9:56 ` fengwang at gcc dot gnu dot org 2005-07-09 12:14 ` tobi at gcc dot gnu dot org 2005-07-12 4:25 ` pinskia at gcc dot gnu dot org 2005-07-12 4:26 ` pinskia at gcc dot gnu dot org 2005-07-12 4:26 ` pinskia at gcc dot gnu dot org 2005-07-14 15:23 ` pault at gcc dot gnu dot org 2005-07-16 20:54 ` pinskia at gcc dot gnu dot org 2005-07-19 8:48 ` fxcoudert at gcc dot gnu dot org 2005-07-19 21:45 ` steven at gcc dot gnu dot org 2005-08-02 10:52 ` fxcoudert at gcc dot gnu dot org 2005-08-06 13:35 ` pinskia at gcc dot gnu dot org 2005-08-31 12:52 ` fxcoudert at gcc dot gnu dot org 2005-09-08 18:51 ` rsandifo at gcc dot gnu dot org 2005-09-09 22:17 ` pinskia at gcc dot gnu dot org 2005-09-09 22:17 ` pinskia at gcc dot gnu dot org 2005-09-12 11:07 ` tobi at gcc dot gnu dot org 2005-09-16 8:57 ` fxcoudert at gcc dot gnu dot org 2005-09-18 19:53 ` tkoenig at gcc dot gnu dot org 2005-09-29 21:33 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20060108104115.31958.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).