Hi,
I'd certainly give another vote towards this being fixed rather than
marked "won't fix". It's the sort of thing one will come across when
using such functions in any kind of programmatic cases where one has 0
values as base cases for some recursive element.
For instance, my work involves satisfiability and boolean functions
and, in particular, when computing certain truth tables, using
cartesian product and then simply adding additional elements to each
list in the product is the simplest way to do this. However, at the
moment, one is forced to add in special checks to ensure the values
are not empty, or 0, to ensure one gets the correct behaviour.
Does anyone really use this incorrect
cartesian_product() = {}
behaviour?
Thanks
Matthew Gwynne
http://cs.swan.ac.uk/~csmg/
On Fri, Jul 2, 2010 at 9:17 PM, Dieter Kaiser <drdieterkaiser at web.de> wrote:
> We have the open bug reports:
>
> ID: 1990099 wrong integer_partitions(0)
> ID: 1993208 cartesian_product incorrect on empyt argument list
>
> The bug reports suggest to do the following changes:
>
> integer_partitions() -> {[]}
> cartesian_product() ?-> {[]}
>
> Furthermore, when we do the above changes we should change the following
> too:
>
> num_partitions(0) ? ? ? ? ?-> 1
> num_distinct_partitions(0) -> 1
>
> I think we have two possibilities:
>
> 1. We close the bug reports as "won't fix".
> 2. We do the suggested changes.
>
> I tend to do the changes.
>
> Opinions?
>
> Dieter Kaiser
>
> _______________________________________________
> Maxima mailing list
> Maxima at math.utexas.edu
> http://www.math.utexas.edu/mailman/listinfo/maxima
>