Files

T

julian.kiedaischandClaude Opus 5.5 95c5b7d97b test(fls): the Java oracle opens files as FILIUS does (M8)

FlsOracle now loads through SzenarioVerwaltung.laden, FILIUS's full
loading path: the archive unpacked, the project's own applications copied
where FILIUS's class loader finds them, then the configuration.
--network keeps the configuration-only load (netzwerkLaden).

On the corpus this changes two files: anwendung_komplett.fls and
multicast_server.fls then have their own applications (Accumulator,
Broadcast) installed. Java's views of the written and the exported files
are byte-equal to before: Java-FILIUS 2.14 opens our exports, with the
classes they carry, as it opens a file of its own, and sees what it sees
in the original. Until own applications on hosts are written (B2), the
reader, writer and export tests leave them out (test/ownApplications.ts);
a test checks that only those two files are touched.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-30 09:32:24 +00:00

ipad-fixtures

test(corpus): 23 .fls files and the Swift reader's view of them

2026-09-29 19:36:37 +00:00

java-examples

test(corpus): 23 .fls files and the Swift reader's view of them

2026-09-29 19:36:37 +00:00

java-tests

test(corpus): 23 .fls files and the Swift reader's view of them

2026-09-29 19:36:37 +00:00

corpus.java.json

test(fls): the Java oracle opens files as FILIUS does (M8)

2026-09-30 09:32:24 +00:00

corpus.swift.json

feat(fls): import the e-mail programs into the editor model

2026-09-30 07:36:05 +00:00

README.md

test(corpus): Java oracle — FILIUS 2.14 reads the corpus itself

2026-09-29 19:49:27 +00:00

README.md

.fls-Korpus

Projektdateien, an denen Lesen und Schreiben gemessen werden. Alle GPL.

Ordner	Herkunft
`java-examples/`	`gitlab.com/filius1/filius`, `beispiele/` @ `6640354` (Filius 2.14.0)
`java-tests/`	ebenda, `src/test/resources/`
`ipad-fixtures/`	`filius-ipad`, `ios/FiliusPadTests/Fixtures/FLS/` @ `3b5ded0`

corpus.swift.json schreibt das Swift-Orakel (npm run oracle): was der Swift-Leser aus jeder Datei macht. Swift ist hier kein Schiedsrichter — er verwirft den Java-Gateway unter der Beschriftung Heimrouter samt seinen Kabeln und Geräte, deren Position XMLEncoder über eine Rückverweis-Kette schreibt (s. Plan §13, M2). Schiedsrichter für das Dateiformat ist Java: corpus.java.json schreibt das Java-Orakel (npm run oracle:java).