Bug 459 - ORB options that accept boolean arguments blindly accept non-boolean values
Summary: ORB options that accept boolean arguments blindly accept non-boolean values
Status: NEW
Alias: None
Product: TAO
Classification: Unclassified
Component: ORB (show other bugs)
Version: 1.0.14
Hardware: All All
: P2 minor
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 2000-02-25 11:47 CST by Ossama Othman
Modified: 2006-04-05 14:06 CDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ossama Othman 2000-02-25 11:47:49 CST
ORB options, such as -ORBDottedDecimalAddresses, that expect boolean arguments
(0 or 1) blindly accept any argument.

Currently all that is done is an atoi() on the argument.  This causes problems
since the following would be valid:

	-ORBDottedDecimalAddresses -ORBDebugLevel 6

The -ORBDottedDecimalAddresses option in this case would not work as expected.
In my opinion, any option that expects a boolean argument should either be
corrected to check if the argument is a valid boolean value, or the boolean
argument should be removed entirely.  There just doesn't appear to be much point
in expecting a boolean argument.  You either supply the argument or you don't.
At the very least, the checking for proper boolean arguments should be
implemented.
Comment 1 Luther Baker 2000-02-25 13:37:59 CST
accepting....
Comment 2 Ossama Othman 2000-04-11 11:45:59 CDT
It looks like Luther accepted this bug but didn't assign it to himself.
Comment 3 Luther Baker 2000-04-20 11:39:59 CDT
My address is luther@cs... I will try to find a way to change it in Bugzilla. I
will also try to fix this ASAP.
Comment 4 Nanbor Wang 2001-10-21 11:25:37 CDT
Anyone knows what is the status on this one? May be a good bug for new comers 
to fix. Can someone please fill in the status?
Comment 5 Johnny Willemsen 2006-04-05 14:06:33 CDT
to the pool