Obsolete way of programming the Amiga
Post date
Thu, 01/02/2025 - 09:37
Is there a list of AmigaOS functions calls that shouldn’t be used in 3.2 when a developer start a new application.?
Things of the past that are needed for compatibility reasons or because higher functions use them internally but that a developer shouldn’t use.
All in all what is the best way to develop under 3.2 and what to avoid.
Post date
Thursday, January 2, 2025 - 20:50
An example that come to mind is GUI programming you don’t want to use Intuition for that like in 1.x days I guess etc
Also for displaying stuff you don’t wanna use a RasInfo, a ViewPort, a ColorMap, a View, and a ViewExtra. Then associatate the ViewExtra to the view, load colors, MakeVPort(), MrgCop(), LoadView() but use OpenScreen or even better OpenScreenTaglist…
Online Status
The OS was mostly well designed from the start so there are not that many API calls to avoid entirely, mostly just things like OldOpenLibrary(), the AVL tree functions in exec.library which are no longer present, Alert() and DisplayAlert() as they don't display properly on RTG systems, etc.
Maybe I should make a full list sometime of all obsolete things including all not just functions but also flags, tags, etc.
>higher functions use them internally but that a developer shouldn’t use.
There's quite a few of these functions too but no need to list them as no application programmers would ever be calling them anyway, they are undocumented for a reason ;-)