9f1a9ae92e
The readlink() function now uses DOS packet I/O instead of trusting Lock() to do the right thing
2025-07-14 13:33:02 +02:00
d9b2c0f38f
Added the header file dependency for the long path handling which makes it build on demand
2025-07-14 13:31:14 +02:00
165232d694
The long path handling code works much better if you actually check it in
2025-07-14 13:29:06 +02:00
7a4966e670
Documentation now covers the most recent handful of changes
...
Details matter: the locale_t definition uses an incomplete structure definition, not an anonymous structure.
2025-07-13 10:59:51 +02:00
dfa3c412d9
The definition of 'locale_t' is now based upon a pointer to an "anonymous" structure
...
Thanks go to sacredbanana for the fix.
2025-07-12 12:30:59 +02:00
f49877920e
sqrt() now returns NAN, rather than 0, if the argument is < 0
...
Thanks go to sodero for providing the fix.
2025-07-12 12:26:34 +02:00
2704ff880f
Implemented the fixes for the tgamma() and tgammaf() functions
...
Thanks go to sodero for providing the fixes.
2025-07-12 12:25:42 +02:00
8378274572
Added support for the "d_type" member of the "dirent" structure.
...
If the '_DIRENT_HAVE_D_TYPE' macro is defined after "#include <dirent.h>" has been used successfully, it means that the "dirent" structure features the "d_type" member. The directory entry type values were adapted from 4.4BSD-Lite2, but not all of these are used.
2025-07-12 12:17:12 +02:00
0e637e9663
usleep() now correctly returns 0, with the function prototype to match
...
This addresses issue #4 by· capehill opened on Jul 30, 2017
2025-07-12 10:15:59 +02:00
a1f85a9c7f
First preparations for a future clib2 release
2025-07-10 14:21:30 +02:00
76d5b5874e
Very minor documentation cleanup
2025-07-10 13:17:30 +02:00
51f88950eb
Copied the changes which introduced ENOTSUP to <errno.h> and the related strerror_r() function.
2025-07-08 14:27:43 +02:00
f9d1222bd7
Fix for wrong address alignment rounding
...
The original V39/V40 amiga.lib puddle creation code did not round up, it rounded off.
2023-10-11 09:15:28 +02:00
d37909e409
Documented why bypassing the read/write buffer is only attempted if there is at least a full buffer worth of data to be read or written.
2023-09-14 09:52:21 +02:00
f5631d8bda
The inner loop of the read operation already fills the buffer as far as it can go. No need to drop into "continue;".
2023-09-11 17:36:32 +02:00
