Subject: UT_Bool vs bool
From: Mike Nordell (tamlin@algonet.se)
Date: Sat Feb 03 2001 - 04:35:42 CST
OK, we have probably concluded that UT_Bool is not really needed anymore.
Should we allow "bool" into the src and just
typedef bool UT_Bool;
#define UT_TRUE true
#define UT_FALSE false
and allow the use of the bool keyword in new files (and allow changing from
UT_Bool to plain bool in exisiting files when anyway editing those)?
I would really like to bring this to an end, not just let it be swept under
the rug again. If we can't agree, at least we know we can't agree and this
wasn't the right time for this "poll" which I think is better than not
knowing the opinions at all.
I also think it would be better if we had a "yes/no/not sure" than plain y/n
since it would at least display the current uncertainty level.
If anyone think a poll is premature, or have any other reservations, please
say so. Otherwise, I'd like to ask:
Should we allow bool?
I say: yes.
/Mike
This archive was generated by hypermail 2b25 : Sat Feb 03 2001 - 04:34:07 CST