Re: [MiNT] LDG guide

[Eero Tamminen <oak@helsinkinet.fi>]

Hi,

On keskiviikko 28 marraskuu 2012, Miro Kropáček wrote:
> nearly exactly a year ago I wrote a document about LDG. It's based on my
> findings, discussions with authors etc.
> 
> Originally I wanted to publish it in LowRes mag but according to guys
> behind the curtain it doesn't seem very much alive, so I decided to
> publish it sooner than last Atari programmer dies ;-)
> 
> I hope you'll find it useful:
> https://docs.google.com/document/pub?id=1d8MSFrcVLW_bLnO7bhokuOTNXoM6yK2p
> Q8O5oyPx9oI(it's public, no google account needed).

I browsed through it and this stuck to my eye:
"Yeah kids, mintlib is huge and bloated in combination with ineffective 
a.out format."

a.out format makes only few bytes difference for a linked program
which is stripped.  MiNTlib using binaries are larger because MiNTlib
has more features than the other libraries.

MiNTlib supports both TOS and MiNT (including a lot of Unix features)
and each piece of functionality isn't fully isolated, they leverage each
other.  Therefore, when linked to a binary, they can also bring to it some
extra functionality that wouldn't necessarily be needed by the application.

I would assume that MiNTlib is much more standards compliant than
e.g. PureC libraries.


	- Eero