> On Fri, 27 Oct 2017, Rugxulo wrote:

> Tiny and Small are better than nothing. AFAIK, DOS-C used to use Small
> model. FreeCOM also uses Small model too, IIRC.

both FreeCOM and Kernel tell the compiler to use the small model
for all default assignments of segments, and use (a lot of) explicit __far
declarations wherever needed.

it's a bit more complicated then using small or large memory models
and leaving complicated stuff to the compiler.

Small model is required to relocate FreeCOM or kernel in memory as
it juggles itself around during swapping and booting.

kernel programmers call it the crazy memory model ;)

> All of the TurboC ports should be deprecated in lieu of OpenWatcom
> (or, better yet, DJGPP).
it's not a TurboC port. in 2001 TurboC was the free (as in beer) compiler
around, and the kernel could only be compiled using TurboC. this
simply still works.

the kernel was then ported to MSC, later to WatcomC.
it will not work with any other compiler without *major* work.
it will never work with DJGPP.

it's like compiling the linux kernel with Visual Studio, even when
both can produce 32bit code.
It's just not going to happen.

>> FreeDOS needs to be "Free".
says who?

>> I know some here
>> have a hard time accepting this, but we really need to focus on using
>> Free tools.
so far this has been decided by those who did the work.

you are not in the position if I should use a hammer or a shovel for
the job to be done.

port whatever software to whatever free compiler you like, and bragg about
it once it's done.

everybody else may feel free to shut up.

I know some here have a hard time accepting this, but FreeDOS is an
engineering problem not a religion.

Amen.


Tom


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to