The program seems to run fine, so it probably is just an code validation of the basex editor.
Verzonden vanaf mijn Galaxy


-------- Oorspronkelijk bericht --------
Van: basex-talk-request@mailman.uni-konstanz.de
Datum: 15-04-2026 12:00 (GMT+01:00)
Aan: basex-talk@mailman.uni-konstanz.de
Onderwerp: BaseX-Talk Digest, V

Send BaseX-Talk mailing list submissions to
basex-talk@mailman.uni-konstanz.de

To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
basex-talk-request@mailman.uni-konstanz.de

You can reach the person managing the list at
basex-talk-owner@mailman.uni-konstanz.de

When replying, please edit your Subject line so it is more specific
than "Re: Contents of BaseX-Talk digest..."

Today's Topics:

   1. Re: cyclic type declarations (Christian Grün)


----------------------------------------------------------------------

Message: 1
Date: Tue, 14 Apr 2026 11:52:02 +0000
From: Christian Grün <cg@basex.org>
Subject: [basex-talk] Re: cyclic type declarations
To: "basex-talk@mailman.uni-konstanz.de"
<basex-talk@mailman.uni-konstanz.de>,  Rob Stapper
<r.stapper@lijbrandt.nl>
Message-ID: <AS4PR09MB55492A0F3328CDF2C67F95F9C7252@AS4PR09MB5549.eurp
rd09.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"

> Just made the next observation: In case of cyclic type declarations the editor throws a "unknown-type:"-error.

I have created a GitHub issue to track this down [1].
Best, Christian

[1] https://github.com/BaseXdb/basex/issues/2635
________________________________________

Von: Rob Stapper via BaseX-Talk <basex-talk@mailman.uni-konstanz.de>
Gesendet: Dienstag, 14. April 2026 09:59
An: basex-talk@mailman.uni-konstanz.de
Betreff: [basex-talk] cyclic type declarations

Hi Christian,

Just made the next observation: In case of cyclic type declarations the editor throws a "unknown-type:"-error.

Module:M0 is a agregate of modules:  M1 and M2, and declares a agregated type using type declarations of both imported modules. Modules M1 and M2 declare ther own type but M2 also imports agregated module: M0. This import of MO in M2 causes in this usecase an "unknown type:-error. This is unwanted.

Hope it is an easy fix.


mvgr.

Rob Stapper

End of BaseX-Talk Digest, Vol 196, Issue 2
******************************************