From owner-freebsd-hackers  Wed Oct 23 04:56:44 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id EAA13921
          for hackers-outgoing; Wed, 23 Oct 1996 04:56:44 -0700 (PDT)
Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA13916
          for <hackers@freebsd.org>; Wed, 23 Oct 1996 04:56:41 -0700 (PDT)
Message-Id: <199610231156.EAA13916@freefall.freebsd.org>
Received: by cheops.anu.edu.au
	(1.37.109.16/16.2) id AA140481805; Wed, 23 Oct 1996 21:56:45 +1000
From: Darren Reed <avalon@coombs.anu.edu.au>
Subject: beef with release engineering.
To: hackers@freebsd.org
Date: Wed, 23 Oct 1996 21:56:44 +1000 (EST)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


For those of us who write software sensitive to changes in include files,
how do we tell FreeBSD versions apart ?

I see __FreeBSD__ (frozen at "2") (in gcc) and __FreeBSD_version, the month
of the release (in osreldate.h).

This isn't nearly useful enough.  Please invent more if possible.
For example, NetBSD has "__NetBSD__" which is the release month and then
a release specific #define, like NetBSD1_2.

Also, it would be nice if including sys/param.h included all the right
files so that you didn't need to explicitly include or look for osreldate.h.
(NetBSD already does this too).

Darren