Hi,
On Sun, Nov 12, 2023 at 5:46 AM Bernd Böckmann via Freedos-devel
wrote:
>
> On 12.11.2023 02:44, Rugxulo via Freedos-devel wrote:
>
> But I still have not found an elegant solution yet to do a widening
> conversion of an untyped pointer from near to far.
> Should be rarely needed though.
And re-mirrored to the FreeDOS Files Archive at Ibiblio. :-)
Thanks!
On Sun, Nov 12, 2023 at 10:24 AM Gregory Pietsch wrote:
>
> Oops! I keep forgetting to change the version numbers in the config.h and
> batch files. Fixed and re-uploaded the files to SourceForge.
> -- Gregory
>
> > On
Oops! I keep forgetting to change the version numbers in the config.h and batch
files. Fixed and re-uploaded the files to SourceForge.
-- Gregory
> On 11/12/2023 11:07 AM EST Jim Hall via Freedos-devel
> wrote:
>
>
> Thanks! I always love a new Edlin release. :-)
>
> I've mirrored it on
Thanks! I always love a new Edlin release. :-)
I've mirrored it on the FreeDOS Files Archive at Ibiblio. Here's the link:
https://ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/edlin/2.23/
For anyone interested, the video Gregory mentioned is here:
https://www.youtube.com/watch?v=yapAepxbaT4
When Jim compiled Edlin 2.22 for the video, I noticed that the OpenWatcom
compiler emitted a warning. Of course, this caused a disturbance in the Force.
The new version 2.23 cleans up that warning, and therefore FreeDOS Edlin can
now be thrown into the gladiatorial arena and slay the software
Hi everyone!
For anyone who needs more info: libmpi is a Multiple Precision Integer
library, and libm is a C math library. Both are public domain. You can
find both on the FreeDOS Files Archive at Ibiblio, under
/files/devel/libs/libm and /files/devel/libs/libmpi. Thanks Gregory!
Here are the
In a world where mathematicians are the lowest of the low, I have sent Jim the
latest versions of these low-level libraries. These versions contain mostly bug
fixes. I am still wondering if someone out there can check the math. -- Gregory___
On 12.11.2023 02:44, Rugxulo via Freedos-devel wrote:
FarAddr internal function
Thanks, that brings me further :-)
I also changed my coding style from a more C oriented style to a more
Pascal like. Unlike in C, one does not have to pass around (explicit)
pointers that often. For example