Re: PIZZA time again :-)
From: mAsterdam <mAsterdam_at_vrijdag.org>
Date: Sat, 03 Sep 2005 12:51:29 +0200
Message-ID: <43197fb8$0$11072$e4fe514c_at_news.xs4all.nl>
>
>
> Ok, then this heuristic might still have bounding conditions that
> describe the points at which it breaks. eg, you reduce two salamis
> to one. if the second salami had come between mozarella and cheeze...
> the example above should mebbe have some more elements, anyways.
Date: Sat, 03 Sep 2005 12:51:29 +0200
Message-ID: <43197fb8$0$11072$e4fe514c_at_news.xs4all.nl>
Duncan Patton wrote:
> mAsterdam wrote:
>>Duncan Patton wrote: >> >>>mAsterdam wrote: >>> >>>>I think >>>>merge([[salami, buttonmushroom, buttonmushroom, mozarella], >>>> [salami, mozarella, onions]], M). >>>> >>>>should succeed with: >>>>M = [salami, buttonmushroom, buttonmushroom, mozarella, onions]. >>> >>> >>>Sure. But why? A consistent rational needs to be included. >> >>It would be consistent with the heuristic 'don't modify input'.
>
>
> Ok, then this heuristic might still have bounding conditions that
> describe the points at which it breaks. eg, you reduce two salamis
> to one. if the second salami had come between mozarella and cheeze...
> the example above should mebbe have some more elements, anyways.
I don't like my pizza's that rich.
Anyway, along the same lines I think:
merge([[salami, buttonmushroom, mozarella],
[salami, mozarella, salami, mozarella]], M).
should give
M = [salami, buttonmushroom, mozarella, salami, mozarella] M = [salami, mozarella, salami, buttonmushroom, mozarella]
or only the first one if the order /of/ (as opposed to /in/) the list matters (see other sub-thread). Another posibility is to disallow conflicting orders in the input (e.g. salami cannot be before and after mozarella in one list). Received on Sat Sep 03 2005 - 12:51:29 CEST