[Top][All Lists]

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

[bug #18995] variable origin changes upon export or unexport

From: Paul D. Smith
Subject: [bug #18995] variable origin changes upon export or unexport
Date: Sat, 10 Feb 2007 18:41:34 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20060601 Firefox/ (Ubuntu-edgy)

Update of bug #18995 (project make):

              Item Group:                    None => Enhancement            
        Operating System:                    None => Any                    


Follow-up Comment #1:

Internally to make, an "undefined" origin means that the variable is not
known to make (when make looks it up in its internal tables, nothing is

Obviously, once you export or unexport a variable, it has to be added to
make's internal tables so make can remember that you marked it as exported or
unexported... so then it's no longer undefined.

I can understand your point, however.  I've marked this as an enhancement
request.  It shouldn't be too difficult to implement: a new origin value for
undefined would need to be added, which is easy... but then all the places
the origin is used would need to be examined to determine if or how they
should react when a variable in this new state is found.

This would also allow us to create a way to "undefine" a variable; currently
once a variable is defined it can never go back to the undefined state again.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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