RE: [boost] filesystem/directory example [was: ... header redux]

From: Stewart, Robert (stewart_at_[hidden])
Date: 2002-04-11 08:44:48

From: Beman Dawes [mailto:bdawes_at_[hidden]]
> 
> At 02:13 PM 4/9/2002, Stewart, Robert wrote:
> 
> I also used to put the output parameters first, but then the 
> STL got me 
> doing it the other way around. I think on balance I like 
> output first, for 
> the reasons you mention.

I'm must be missing something.  How does the STL get you to put output
parameters last?  The only think I can think of is with predicates, and few
(any?) of them are passed as non-const references such that they contain
potentially new state after the function call.

>  >Looking at this code, I find myself a bit confused by the 
> terminology you
>  >have selected.  I was troubled when I read your list (on 
> the filesystem
>  >design page you posted), but didn't quite know what was wrong.
> 
> I'm not entirely happy with terminology either.
> 
> I spent some time reading the POSIX definitions at 
> http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap03.html
> 
> I really don't see them as any less confusing, although it 

Those say pretty much what I said.  Notably, Posix doesn't define "path,"
which I did.

> might be better 
> to just go with a standardized terminology. So for now, exact 
> terminology 
> remains an open issue.

"Standard terminology" is the same sort of argument for sticking with
printf()-style formatting in the format library.  I should think it would
apply equally well here unless someone presents a better idea.

Rob
Susquehanna International Group, LLP
http://www.sig.com

IMPORTANT:The information contained in this email and/or its attachments is
confidential. If you are not the intended recipient, please notify the
sender immediately by reply and immediately delete this message and all its
attachments.  Any review, use, reproduction, disclosure or dissemination of
this message or any attachment by an unintended recipient is strictly
prohibited.  Neither this message nor any attachment is intended as or
should be construed as an offer, solicitation or recommendation to buy or
sell any security or other financial instrument.  Neither the sender, his or
her employer nor any of their respective affiliates makes any warranties as
to the completeness or accuracy of any of the information contained herein
or that this message or any of its attachments is free of viruses.