importProject turns a PC's or notebook's Java file tree into Swift's virtual file system, as Swift's registerVirtualFileSystem does: images by type or extension from Base64, text by type, unknown types as binary data or text, unsafe names and collisions left out with a warning, and the whole import rejected over the project quota. NSString.pathExtension is measured in the oracle, which now writes every imported file system. On the 13 files Swift reads completely every file matches, images compared by hash. Intended: a host whose file has no file system stays empty, as in Java, where Swift adds the demo files of a new device. Pending the applications step, the comparison reads our /webserver as Swift's /www and leaves out the e-mail and Gnutella state 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).