From owner-freebsd-hackers  Sat Apr 22 20:16:30 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id UAA12227
          for hackers-outgoing; Sat, 22 Apr 1995 20:16:30 -0700
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA12221
          ; Sat, 22 Apr 1995 20:16:29 -0700
Received: (from julian@localhost) by ref.tfs.com (8.6.8/8.6.6) id UAA25429; Sat, 22 Apr 1995 20:16:29 -0700
From: Julian Elischer <julian@ref.tfs.com>
Message-Id: <199504230316.UAA25429@ref.tfs.com>
Subject: Re: Any objection to adding a .undef(VARNAME) to make?
To: jkh@freefall.cdrom.com (Jordan K. Hubbard)
Date: Sat, 22 Apr 1995 20:16:28 -0700 (PDT)
Cc: hackers@freefall.cdrom.com
In-Reply-To: <24740.798506728@freefall.cdrom.com> from "Jordan K. Hubbard" at Apr 21, 95 04:25:28 pm
Content-Type: text
Content-Length: 487       
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

submit it back to 'CSRG' (?!) 
> 
> The subject says it all..
> 
> I've long been bothered by bmake's inability to programmatically unset
> a variable.  Assuming that nobody feels it to be too evil a hack to
> live, are there any objections to using the keyword `.undef'?
> 
> Yes, it will make us non-standard, but we're essentially ALREADY
> non-standard due to having a build system from hell that nobody else
> is going to adopt without taking our make, too.
> 
> 					Jordan
> 
>