> Whoa there! -- I take serious issue with the statement
> that- "Its an OO Class...and should use exceptions".
> The C++ spec and programming compuity at large has
> recognized that exception handling is NOT designed
> for anticipated flow control but instead for truly "exceptional
> conditions". The fact that the URI class explicitly ecpects
> path names and throws an exception in this case is, I believe,
> something that could be fixed up a bit. I think the root cause
> is excessive work done in the constuctor. This makes you
> _need_ to throw an exception for convenient signalling to
> consumer code - not because you encountered an
> "exceptional situation".
>
But its NOT written to take files paths and throw an exception if its not.
It written to protect itself from badly formed URLs or plain junk, and the
parser is just using in a way that makes it seems like that. The parser
could pass it what it feels is a perfectly good URL and it could still be
badly formed and that needs to be recognized and reported, and via an
exception since that's how errors are reported in the parser.
--------------------------
Dean Roddey
The Charmed Quark Controller
Charmed Quark Software
[EMAIL PROTECTED]
http://www.charmedquark.com
"If it don't have a control port, don't buy it!"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
