bug-make
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #32307] Documentation does not identify versions at which new featu


From: marvin greenberg
Subject: [bug #32307] Documentation does not identify versions at which new features became available
Date: Mon, 31 Jan 2011 18:06:43 +0000
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10

URL:
  <http://savannah.gnu.org/bugs/?32307>

                 Summary: Documentation does not identify versions at which
new features became available
                 Project: make
            Submitted by: marvingreenberg
            Submitted on: Mon 31 Jan 2011 06:06:42 PM GMT
                Severity: 3 - Normal
              Item Group: Documentation
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
       Component Version: 3.82
        Operating System: None
           Fixed Release: None
           Triage Status: None

    _______________________________________________________

Details:

Many versions of make are still in circulation, driven by the frameworks
(cygwin) and operating systems that include make.  Although it is possible to
always upgrade to make.latest, it may not be practical.

Conditionals $(and) and $(or) were added with make 3.81, $(eval) and $(value)
with 3.80, various others presumably.

Propose that new features or changes behavior be documented with a small
comment like (Conditionals 'and' and 'or' were added at version 3.81).  This
is similar to the approach taken by python and java.

Essentially the same information IS available in a source distribution in
NEWS, but adding this information to the documentation would make supporting
makefiles in the presence of multiple versions of GNU make more natural.

I suppose I should attach a patch.  Maybe I'll do that if there is any
support for the idea.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?32307>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]