public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/33456]  New: Vendor extension: Use env. var.  to set filename of preconnect unit
@ 2007-09-17 18:13 burnus at gcc dot gnu dot org
  2007-09-17 19:22 ` [Bug fortran/33456] " kargl at gcc dot gnu dot org
  2007-09-23  9:32 ` fxcoudert at gcc dot gnu dot org
  0 siblings, 2 replies; 3+ messages in thread
From: burnus at gcc dot gnu dot org @ 2007-09-17 18:13 UTC (permalink / raw)
  To: gcc-bugs

Some vendors seemingly offer to set the filename of a pre-connected unit via an
environment variable.

I'm not sure we need this, but some other compilers seem to have it and it is
seemingly used:

http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/16d2c1d82a05edb4


-- 
           Summary: Vendor extension: Use env. var.  to set filename of
                    preconnect unit
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33456


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug fortran/33456] Vendor extension: Use env. var.  to set filename of preconnect unit
  2007-09-17 18:13 [Bug fortran/33456] New: Vendor extension: Use env. var. to set filename of preconnect unit burnus at gcc dot gnu dot org
@ 2007-09-17 19:22 ` kargl at gcc dot gnu dot org
  2007-09-23  9:32 ` fxcoudert at gcc dot gnu dot org
  1 sibling, 0 replies; 3+ messages in thread
From: kargl at gcc dot gnu dot org @ 2007-09-17 19:22 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from kargl at gcc dot gnu dot org  2007-09-17 19:22 -------
I would strongly discourage adding this feature.  A long time ago,
either Paul Brook or Steven Bosscher and I exchanged email about
the use of environmental variables to control various aspects of
gfortran.  In the end, I recall that we agreed a proliferation of
environmental variables could lead to a maintenance nightmare.

But, as usual if someone implements the feature, I won't stand in 
the way.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33456


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug fortran/33456] Vendor extension: Use env. var.  to set filename of preconnect unit
  2007-09-17 18:13 [Bug fortran/33456] New: Vendor extension: Use env. var. to set filename of preconnect unit burnus at gcc dot gnu dot org
  2007-09-17 19:22 ` [Bug fortran/33456] " kargl at gcc dot gnu dot org
@ 2007-09-23  9:32 ` fxcoudert at gcc dot gnu dot org
  1 sibling, 0 replies; 3+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2007-09-23  9:32 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from fxcoudert at gcc dot gnu dot org  2007-09-23 09:32 -------
Tobias says "I'm not sure we need this", and Steve rightly points out that this
was ruled out in the past. So, closing for now. (If the need arises, we should
first discuss it on the list, IMHO.)


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WONTFIX


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33456


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-09-23  9:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-09-17 18:13 [Bug fortran/33456] New: Vendor extension: Use env. var. to set filename of preconnect unit burnus at gcc dot gnu dot org
2007-09-17 19:22 ` [Bug fortran/33456] " kargl at gcc dot gnu dot org
2007-09-23  9:32 ` fxcoudert at gcc dot gnu dot org

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).