Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge devel (ie. release 0.9.0) to the master #84

Merged
merged 461 commits into from
Feb 20, 2025
Merged

Merge devel (ie. release 0.9.0) to the master #84

merged 461 commits into from
Feb 20, 2025

Conversation

t-w
Copy link
Collaborator

@t-w t-w commented Feb 20, 2025

Merging all released code for 0.9.0 (+ 1 recent change: c0fa479) to the master.

t-w added 30 commits February 21, 2024 12:21
For better type safety. Also, renamed to separate the namespace.
…ties.

This is done to distinguish the functions for checking the type
of the filesystem from the functions for checking its properties.
(Both regarding the original A. DOS filesystems.)
…unctions.

Separating ADFlib's namespace, better type safety.
With static locals, the results of concurrent calls are unpredictible.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
These arrays are in file header blocks and file ext. blocks.
(Separating ADFlib's namespace).
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
Separating ADFlib's namespace.
t-w and others added 27 commits May 15, 2024 19:50
And some minor corrections in testing with autotools section.
Also, correct sources that were relying on that.
Remove unneeded include (not even exising anymore...).
2 unit test were using the same adf filenames as test
devices, so the tests, when executed in parallel
(building debs) were failing. Fixed making unique filenames.
Library headers listed as _HEADERS are being installed along
with the library, while the private sources should not
(they are needed only for building the library itself).
Such private headers can be specified as noist_HEADERS, or,
what is recommender by Automake manual, just as _SOURCES.

Note, that if the private headers are completely omitted,
make distcheck fails.
The DLL export prefix is required only in headers (in declarations).
The tested function is from a private library module, it is not
exported by the library, so the module must be linked directly.
Lintian complained about privacy breach.
When appending data to an existing OFS block, the dataSize field in
the block header wasn't being extended. So if you wrote a file via
fuseadf, 4Kb at a time, then the first 4Kb write would terminate in
mid-block leaving that block's dataSize indicating that it was half
full; then the second 4Kb write would write the first part of its data
into the partial block but leave that block's dataSize field
unchanged. An emulated Workbench 1.3 era Amiga would honour the
dataSize field and treat the partial block as short, losing the
initial segment of the second 4Kb of the source file.
adfFileWrite: update dataSize when extending an OFS block.
@t-w t-w requested a review from lclevy February 20, 2025 12:32
@t-w t-w merged commit dd2f831 into master Feb 20, 2025
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants