Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 25 Feb 2001 00:07:01 -0800
From:      Kris Kennaway <kris@obsecurity.org>
To:        Matt Dillon <dillon@earth.backplane.com>
Cc:        Bruce Evans <bde@zeta.org.au>, Robert Watson <rwatson@FreeBSD.ORG>, Nick Sayer <nsayer@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, arch@FreeBSD.org
Subject:   Re: cvs commit: ports/astro/xglobe/files patch-random
Message-ID:  <20010225000701.B10488@mollari.cthul.hu>
In-Reply-To: <200102250725.f1P7PVs12297@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Feb 24, 2001 at 11:25:31PM -0800
References:  <Pine.BSF.4.21.0102251713590.5810-100000@besplex.bde.org> <200102250640.f1P6e0q11960@earth.backplane.com> <20010224225935.A769@mollari.cthul.hu> <200102250725.f1P7PVs12297@earth.backplane.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--RASg3xLB4tUQ4RcS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 24, 2001 at 11:25:31PM -0800, Matt Dillon wrote:

> :This isn't true -- as it stands now, people are writing code which
> :produces bad behaviour (e.g. the xglobe stars thing), or is insecure,
> :because they are ignoring the documentation.  If we add a link-time
> :warning it will probably catch more software writers, and the net
> :result is positive.  It also points out instances of possibly bad
> :software which FreeBSD porters and committers can address, again a
> :positive change.  It wastes no-one's time except about 30 seconds of
> :mine, which I was happy to give :-)
>=20
>     All that adding a compile-time warning will do is annoy anyone trying
>     to use the interface legitimately.  If you have a problem with a
>     particular programmer's use of the interface, you should email that
>     programmer.  We are not responsible for programmers who ignore=20
>     documentation.  While it is nice to have some warnings in there,
>     there is a limit to what we should be doing to save the programmer
>     from himself.  Many of these people aren't even using FreeBSD, so
>     I really doubt that adding #warnings to our compilation environment
>     will actually do what you think it will do, especially in regards
>     to ports.

Yes, many software authors don't use FreeBSD, but many do, and the
second benefit I pointed out above stands.

>     People have gone overboard before... the strftime() warning, for
>     example, is extremely annoying to me because I am using strftime()
>     exactly the way it is documented to be used.  Some overzealous bozo
>     decided the best way to warn everyone about Y2K was to cause the
>     compiler to spew warnings out from 2-digit years formatted with
>     strftime().  Bah.  What you are proposing here is something of the
>     same ilk.

Stop complaining to me about strftime, it's not the same thing.

Kris

--RASg3xLB4tUQ4RcS
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE6mL0lWry0BWjoQKURAo6pAKDl/mb1qAa5ddux7g6iDnrXfr8qqQCgviz+
Kd4LGPtHLdMw5NCzpBe7wc0=
=WSFn
-----END PGP SIGNATURE-----

--RASg3xLB4tUQ4RcS--

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010225000701.B10488>