[MiNT] WCOWORK operating mode

["Joakim Högberg" <gokmase@gmail.com>]

Hi all,

>> I have only a wish: "don't break the compatibility".
>Well, if thats the only concern, then we dont have a problem!

I am beginning to realize that the way the new mode works is something
that very few have understood!

>How would this new operating mode break compatibility? You can use it
>or not.
>If you like it and think it will ease your programming: Use it!

Ok, if I get this right, then the new workmode is:

1) 100% optional. The app will report to the AES that it supports the new mode
(if it does, of course), and if so the AES will let the app take advantage of the new mode. Right?

2) 100% compatible. If an application does not explicitly support it, the AES will allow the app to
work as before. That is, the default behaviour is the way it works in other AES's now. Right?

3) A very clever extention of the way the AES works, since it allows new software to exploit it,
whereas at the same time it is not being forced upon the programmer to do so! What is the setback?

I can only assume that those that are so hostile to this new addition have not fully understood the concept,
or that there is some hidden reason why the idea would cause problems.

>If you dont like it and see no benefit: Dont use it!
>It is as simple as that!

If this is for sure the case, I think we can put an end to the current discussion regarding whether
the support for eg. MagiC and N.AES should be a problem? I mean, if the new additions in no way
breaks compatibility it seems plain silly to fight over it, right?

>I dont think ozk wants to get rid wind_calc entirely. Well, yes, maybe
>in new apps, where it can be avoided. But it has to be there all the
>time otherwise a whole big bunch of software would be ruled out
>immediately - and no one wants that!

And if I understand things correctly, then even the first example of a program taking advantage of the
new mode (toswin & qed) still has the support set as optional. If you wish to save some extra Kb by
only using the new mode in those apps, you need to specify this when compiling. Unless you do, these
apps will still be working as before. Under all AES's that is has supported until now. (Hope I got that right too, Odd?)

In short:

* WCOWORK operating mode should only be used for apps that requests it directly by sending the
approprite AES call.

* WCOWORK operating mode should not be used for apps that has not sent this AES call.

*Programs in FreeMiNT CVS like Qed and Toswin will still be compatible with AES's that does NOT support
WCOWORK operating mode. People who wishes to have a more stripped binary for XaAES, can however
decide to compile binaries that supports WCOWORK operating mode exclusively.


-If I have understood any aspect of this implementation incorrectly, someone please correct me!


Regards,

/Joakim