English Amiga Board

English Amiga Board (http://eab.abime.net/index.php)
-   Coders. System (http://eab.abime.net/forumdisplay.php?f=113)
-   -   DoSuperMethodA without amiga.lib (http://eab.abime.net/showthread.php?t=104863)

kamelito 05 December 2020 21:56

Morphos is using Objective C, why not AmigaOS.
https://www.morphos-team.net/guide/objective-c

bloodline 05 December 2020 22:03

Quote:

Originally Posted by kamelito (Post 1444665)
Morphos is using Objective C, why not AmigaOS.
https://www.morphos-team.net/guide/objective-c

OMG!! Yes that exactly how I imagined BOOPSI to be implemented properly! :agree

-edit- it looks like they have written their own Obj-C runtime, that’s quite heavy going... I use Obj-FW if I need a runtime on a non-gnustep/non-Mac platform!

Minuous 06 December 2020 02:22

Quote:

Originally Posted by bloodline (Post 1444640)
AmigaOS is somewhat unusual as the basic operating system remained unchanged for 30 years... only now is AmigaOS 3.1 being updated. As such the API/ABI is literally etched in stone. Make a change now and you burn 30 years of legacy rather than maybe five years...

That's not correct.

bloodline 06 December 2020 11:07

Quote:

Originally Posted by Minuous (Post 1444691)
That's not correct.

That’s a fair point! Microsoft actually adopted the strategy of keeping 30+ year old operating system components in their products. And it’s worked well for them. But this is certainly off topic, with little to do with BOOPSI.

Minuous 06 December 2020 12:02

My point wasn't about Microsoft, it was development continued beyond 3.1. Eg. OS3.5 and 3.9 have a full set of BOOPSI classes, which 3.1 lacks.

bloodline 06 December 2020 12:15

Quote:

Originally Posted by Minuous (Post 1444725)
My point wasn't about Microsoft, it was development continued beyond 3.1. Eg. OS3.5 and 3.9 have a full set of BOOPSI classes, which 3.1 lacks.

But the underlying architecture of how BOOPSI works has remained unchanged for 30 years! All the flaws and bugs are now part of the design, which (as meynef pointed out) has some advantages that they are at least known and work arounds have become standard part of the architecture, but also limits future development.

Thomas Richter 06 December 2020 13:44

Quote:

Originally Posted by bloodline (Post 1444727)
All the flaws and bugs are now part of the design, which (as meynef pointed out) has some advantages that they are at least known and work arounds have become standard part of the architecture, but also limits future development.


Well, I would not call them "bugs" (of course, we have that, too), but "design issues". They cannot be fixed anymore. We have the same thing in the dos.library with its Tripos legacy.


All times are GMT +2. The time now is 09:39.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.

Page generated in 0.04525 seconds with 11 queries