|
Boost : |
From: Thomas Witt (witt_at_[hidden])
Date: 2002-07-24 14:58:42
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Beman,
On Saturday 20 July 2002 02:40, Beman Dawes wrote:
>
> That's a long way of saying that class path really needs some standard
> library container-like functions, or maybe a way to export a
> container. The path::empty() function came about because I got tired of
> writing (for path foo):
>
> if ( foo.generic_path().empty() ) ...
>
> And wanted to write instead:
>
> if ( foo.empty() ) ...
>
> The name "empty" came from the same function in standard library
> containers.
>
> Anyhow, it may be easier to know what to do about path::empty() once the
> question of how to provide a container-like (rather that the current
> string-like) views of the contents of a path.
My main concern was not the need for both functions. It is just that I think
from a usability point of view it is inacceptable that they have the same
name.
- --Thomas
- --
Dipl.-Ing. Thomas Witt
Institut fuer Verkehrswesen, Eisenbahnbau und -betrieb, Universitaet Hannover
voice: +49(0) 511 762 - 4273, fax: +49(0) 511 762-3001
http://www.ive.uni-hannover.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9Pwb20ds/gS3XsBoRAjwkAJ4ke7jtbwfdtNAZr81EXF0Y1M9arwCdEtn8
UYSM3E2ZQRcshWBtnT+ydd8=
=BT43
-----END PGP SIGNATURE-----
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk