Ghislain, yes, what you say makes sense, given the current
implementation. But the current API reflects our long-term goal of
separating zorba from the store (into separate libraries).  The
application may link with several stores and start zorba with a
different store each time. In this scenario, the store must be passed as
an input to zorba.

You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.

  ZorbaImpl::init might call GlobalEnvironment::init with a NULL store

Status in Zorba - The XQuery Processor:
  Fix Committed

Bug description:
  At this location, in function ZorbaImpl::init(Store* store):

  The assertion

  assert(store == NULL || store2 == store);

  allows the variable store to be NULL (and there are places that do
  call this function indirectly with an explicit NULL store pointer,
  such as here:


  However, this assertion is followed by


  that always fails upon a NULL pointer.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to