I have added a GitHub issue for the CHOP option:
https://github.com/BaseXdb/basex/issues/913
I invite all of you to add comments, report on potential difficulties
caused by the switch, etc.
Christian
On Wed, Mar 26, 2014 at 7:10 PM, Dirk Kirsten d...@basex.org wrote:
Hi Graydon,
as
Envoyé : jeudi 27 mars 2014 14:03
À : Dirk Kirsten
Cc : BaseX
Objet : Re: [basex-talk] Fwd: Re: whitespaces in import
I have added a GitHub issue for the CHOP option:
https://github.com/BaseXdb/basex/issues/913
I invite all of you to add comments, report on potential difficulties caused
Sorry, mail was supposed to be send to the mailing list... Information
is the same as in Leos mail
Original Message
Subject: Re: [basex-talk] whitespaces in import
Date: Wed, 26 Mar 2014 17:59:12 +0100
From: Dirk Kirsten d...@basex.org
To: Stefan Sechelmann
True; this discussion is already going on for quite a while now. The
default value of CHOP will be changed in a future version of BaseX.
On Wed, Mar 26, 2014 at 6:14 PM, Graydon Saunders graydon...@gmail.comwrote:
Though I think CHOP defaulting to true is a bug compared to the
expected
Could we get _which_ future version? I recall this being said before
7.8 was released, too, and was feeling hopeful.
I understand that from a technical perspective this is a completely
trivial thing -- set the flag! -- but from the perspective of having
to argue for three months to be able to
Hi Dirk --
I understand that you don't want to break backward compatibility, but
a)it never gets easier, only harder, when you must do that, as more
existing applications accumulate and b)the example given of the type
of problem is seriously bad code. (I totally believe this kind of
code exists
Hi Graydon,
it is not so easy. For instance: The moment I turned off CHOP during import
of my test data base, all of my unit tests involving assert-equals with a
comparison
of nodes failed because of extra of different whitespace. So this has indeed
deep
implications for running code.
Stefan
Graydon,
It's a plain fact that we can't simply switch the default behavior of
BaseX, because there are various applications out there that first need to
be checked in depth before we can realize the switch. We simply need
(..enough..) time to get aware of the consequences before we do simple
Hi Graydon,
as already said, we are going to change the default and we are aware of
the problem.
But I do think your statement that this is an error and we are
preserving errors does not hold. As Liam Quin pointed out at
https://mailman.uni-konstanz.de/pipermail/basex-talk/2013-April/004983.html
9 matches
Mail list logo
