Re: Q: type ... is new String

[Georg Bauhaus <rm.dash-bauhaus@futureapps.de>]

On 07.06.12 01:56, Randy Brukardt wrote:
> "Georg Bauhaus"<rm.dash-bauhaus@futureapps.de>  wrote in message
> news:4fcdf97f$0$9521$9b4e6d93@newsspool1.arcor-online.net...
>> On 05.06.12 11:06, Dmitry A. Kazakov wrote:
>>
>>>> (All I see is subsequences of 2#bbbb_bbbb#. For the AI part,
>>>> I am told to produce the most likely information that the
>>>> originator might have intended to send.)
>>>
>>> Bad design. Don't do that.
>>
>> How is producing the most likely information from a piece
>> of data bad design? And who am I to say "I don't do that"?
>
> It's bad design. Malformed input should always be rejected, period. Any
> other situation leads to zillions of security holes. And if you're not
> willing to say "don't do that", let me do so for you. :-)

Thanks. However, technical considerations are only one of the inputs
to the utility function that maps from the multidimensional space of
business factors into money. If to reject means values further away
from its maximum, I can't reject. A better internet is not the
immediate business model, as usual. Nor would the garbage care
if one of its copies was rejected by our programs. ;-)

In my case, the programs have to operate like a very small Google:
They shall find interesting information in all the garbage precisely
because combinations of bits of information in there may turn out to be
worth the effort (i.e., the money). Pragmatic requirements, yes,
and they influence the "design". So strings it is, for the most part.