Date: Tue, 26 Feb 2013 21:13:03 +0100 From: Davide Italiano <davide@freebsd.org> To: d@delphij.net Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Xin LI <delphij@freebsd.org>, John Baldwin <jhb@freebsd.org> Subject: Re: svn commit: r247300 - in head: sys/sys usr.bin/truss Message-ID: <CACYV=-Hjp_=k9fu_8PNUB%2BY7AhF6AFf3oX1-LYM0TgOSu8Jodw@mail.gmail.com> In-Reply-To: <512D071E.8090306@delphij.net> References: <201302260213.r1Q2D2N1016801@svn.freebsd.org> <201302260941.52534.jhb@freebsd.org> <CACYV=-E2LddT1jmjvFTLsq_NymbxrEvHL9w4SCOZaVhGGy2p=Q@mail.gmail.com> <512D071E.8090306@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 26, 2013 at 8:03 PM, Xin Li <delphij@delphij.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 02/26/13 09:09, Davide Italiano wrote: >> On Tue, Feb 26, 2013 at 3:41 PM, John Baldwin <jhb@freebsd.org> >> wrote: >>> On Monday, February 25, 2013 9:13:02 pm Xin LI wrote: >>>> Author: delphij Date: Tue Feb 26 02:13:02 2013 New Revision: >>>> 247300 URL: http://svnweb.freebsd.org/changeset/base/247300 >>>> >>>> Log: Expose timespec and timeval macros when __BSD_VISIBLE is >>>> defined. This allows userland application to use the following >>>> macros: >>>> >>>> timespecclear, timespecisset, timespeccmp, timespecadd, >>>> timespecsub; >>>> >>>> timevalclear, timevalisset, timevalcmp. >>> >>> Why not fix truss to use the stock functions instead of keeping >>> private "unusual" versions? >>> >>> -- John Baldwin >> >> time.h is already a mess in terms of namespace pollution, and this >> exposure might not help thing. Other details here: >> http://permalink.gmane.org/gmane.os.freebsd.architechture/15518 > > What would be the preferred way of doing these operations on a > timespec structure then? Should the caller duplicate these macros? > > Cheers, > - -- > Xin LI <delphij@delphij.net> https://www.delphij.net/ > FreeBSD - The Power to Serve! Live free or die > -----BEGIN PGP SIGNATURE----- > > iQEcBAEBCgAGBQJRLQceAAoJEG80Jeu8UPuzYQIIAIf9vJ6TS2Lmk+vkC0O9oXFi > 1W+msaOn/Onhi9TSbpdPlhfQI2VB8bkdDCA63ll3LC64jjDaRObobSYxYn7mKhz9 > +o0sdRXl8AvDkHNofSmrtO0h3JormzJjGIxNLi0DsTgrUDuOiVT34WtzTY6uvvnG > Y4zpxoY/KI9ftaAabxhfTG8RcMkWbAHrQXmah/UujuMID57665I0NwxBap5lyyng > lMygEBfAZ8bZqbh2IcUZi9qKBsIkFJugxYZc95WkU73A4rCGBJSJXpYWAghJxthy > nDHNA6I5DxoeXpf3hEscG4WjHgLubZen8HwEs/3uA4mRkmAkI7pwT56wo7kVnwU= > =JZjk > -----END PGP SIGNATURE----- Well, it may be. And maybe this might be a topic for a larger discussion. What's your use-case? -- Davide "There are no solved problems; there are only problems that are more or less solved" -- Henri Poincare
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACYV=-Hjp_=k9fu_8PNUB%2BY7AhF6AFf3oX1-LYM0TgOSu8Jodw>