Re: Q: type ... is new String

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

On 05.06.12 09:32, Dmitry A. Kazakov wrote:
> On Mon, 04 Jun 2012 22:56:01 +0200, Georg Bauhaus wrote:
>
>> On 04.06.12 19:05, Dmitry A. Kazakov wrote:
>
>>> There is nothing ambiguous in character encoding,
>>
>> In processing data from any source that speaks HTTP, you don't really know
>> the character encoding: you may be told the encoding is X but actually it
>> is Y.
>
> <=>  I do know the encoding.

You snipped the part that explained how this "knowledge" isn't
knowledge. It is in a state of flux and occasionally crystallizes
to yield Heisentypes. ;-)

(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.)


> You are trying to pursue some absolute truth, e.g. "true encoding" of a
> broken page, which simply does not exist and is irrelevant.

I am the one to create the truth, the valuable information. Like I am
the one to guess the correct interpretation of calendar date 5/6/7.

> Note again a connection to error checks: the program shall not check
> itself. A consequence of this: if you use an input it is not your
> responsibility to make guesses.

Yes, it is, making guesses is precisely what I'm told to do.

> If you want to add some encoding guessing layer, do it just elsewhere.

Too late. Too many additional decisions that create a large set
of types in layers that isn't lightweight enough to handle
within the constraints of the job. And the process of type
creation will need backtracking triggered by unexpected events.

>>> For each possible input
>>> there is a defined output the parser should spill. Where is a problem?
>>
>> Here is the problem: There is no complete description of the set of
>> possible inputs.
>
> See, that is the problem. People didn't do their job.

No, they did their job. What they did might not be like
what I wish they had done. But a doctor cannot sit back
and accuse the patients of having ruined their own health.
*That* is irrelevant.


> Nope, things changing are as irrelevant as the computer's relative position
> to Proxima Centauri.

So what is the outline of a type that describes a file naming
scheme that has changed?