Java's DNS server reads its records from the text file /dns/hosts on every query. dnsHosts.ts ports that reading (DNSServer.leseRecordListe, ResourceRecord, Dateisystem.holeDatei) and keeps in the model the records Java answers: type exactly A, MX or NS, and a name Java accepted. The file stays in the file system as it is. Both oracles read 76 hand-picked hosts files (dns-hosts.cases.txt): the Java oracle through DNSServer.holeResourceRecords (DnsHostsCases), the Swift oracle through TopologyDNSHostsFileCodec (--dns-hosts). The Java view matches Java on every case; the model matches Swift except for 33 named cases in twelve reasons: Java splits at single spaces and LF only, has no comments or "IN", turns a TTL that is no int into 3600, keeps duplicates, and empties names with a leading digit. The Swift dump now carries each server's records; the corpus comparison covers them on 16 files. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
.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).