A while back I was granted co-maintenance of Algorithm::QuineMcCluskey. It
handles one Boolean expression at a time, and I decided that it would be
good to create a package that could manipulate a Boolean truth table.
So Boolean::TruthTable is nearly ready to go (I have documentation to
complete).
But, to handle the columns in the table, I created a base class.
Algorithm::QuineMcCluskey would become a child of this class (because
after all this is done, I'm going to explore other algorithms).
Naming this class is a little trickier. It's not an algorithm, so I don't
think using the Algorithm top level is appropriate. I'm settling on
Boolean::Minimizer (which is what the algorithms do).
Now the potential problem is that Boolean isn't used much as a top-level
name. I can only find 'boolean', the pragma for using true and false
values, and Boolean-String, which has a 0.01 release and hasn't been
updated since.
So are there any objections to my using Boolean as a top level name in
earnest?
-john
