On 06/07/2007 10:34 PM, Stefan Manegold wrote:
--
Sjoerd Mullender
> On Thu, Jun 07, 2007 at 08:01:52PM +, Sjoerd Mullender wrote:
>> Update of /cvsroot/monetdb/pathfinder/compiler/semantics
>> In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv31053
>>
>> Modified Files:
>> Tag: XQu
On Thu, Jun 07, 2007 at 08:01:52PM +, Sjoerd Mullender wrote:
> Update of /cvsroot/monetdb/pathfinder/compiler/semantics
> In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv31053
>
> Modified Files:
> Tag: XQuery_0-18
> xquery_fo.c
> Log Message:
> Experiment: split up declar
Jan,
property checking is quite expensive, hence, you might want to do it for
debugging purposes, only, e.g, when property checking is enabled in Mserver
via --debug=8 / --debug=10.
To do so, just replace
"if ( 1 )"
by
"PROPDEBUG"
(which is defined as "if (GDKdebug & PROPMASK)"
Jan,
IMHO, this changes is not correct.
Though being of type BIT (which is physically a signed char, hence 8 bit
wide), the ordered flags use all 8 bits, only the lowest one (1) indicates
sortedness, the highest one (1<<7=128) indicates reverse sortedness, and the
remaining ones are "mis-"used fo
Hi Jens,
Thanks for the attention. I think this replaceEntities flag indicates if
user defined entities should be replaced by their entity value. This is
always false for the default XML entities. When I look at the variable at
runtime it is 0. But it does call getEntity() to replace te value
Hi Jan F,
thanks for looking into our shredder's entity handling. This has been
bugging us for quite a while now.
It feels a bit strange, though, that we really have to implement
getEntity() ourselves. After all, this is exactly what I would expect
to be handled automatically by an XML parsing
