From owner-cvs-all  Thu Apr 23 06:16:30 1998
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA28265
          for cvs-all-outgoing; Thu, 23 Apr 1998 06:16:30 -0700 (PDT)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28257
          for <cvs-committers@FreeBSD.ORG>; Thu, 23 Apr 1998 06:16:20 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA24750;
	Thu, 23 Apr 1998 23:12:31 +1000
Date: Thu, 23 Apr 1998 23:12:31 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199804231312.XAA24750@godzilla.zeta.org.au>
To: dufault@hda.com, eivind@yes.no
Subject: Re: cvs commit: src/sys/sys time.h
Cc: cvs-committers@FreeBSD.ORG
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

>> Given no specification for timerclear pre-existing behavior
>> should be maintained.
>
>Pre-existing behaviour was added two weeks ago, and was wrong at that
>point (a non-parenthesized expression).  I did the change the day

timerclear() is standard in at least Net/2 BSD-4.4Lite[1-2].  It is
now only a compatibility interface in FreeBSD.  Perhaps it is never
used.

Only timevalclear() and timespecclear() were added two weeks ago.
You didn't change those.  They are kernel-only so they are safe
to change.  Perhaps they should never have been (unsafe) macros
anyway.

>> Given a specification that says it behaves as if it returns void
>> you're right.
>
>AFAIK, the only specification for timerclear() is the code.  The code
>says it returns void.  Happy?  ;-)

The code said that was an expression with side effects, value 0 and
type long.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message