not_ginger_matt wrote>" You [AMS] are assuming that OEM customers want to run 100% of their own code all the time."
How so? It was Ad6 that pointed out that some of their OEM customers required that additional checking be performed - and Ad6 had ROL implement this. I can't say if that means the OEM customers will *always* use only their own code or not.
not_ginger_matt wrote>"If I write a module and don't specify it as 32-bit then it won't run on Select-32 or RISC OS 5. And yet if I package it as an application you think it should? To me that doesn't make Select-32 look deficient, it makes RISC OS 5 look plain stupid. "
Modules are in effect operating system extensions, they have access to a lot of low level stuff - module checking therefore *does* make sense. An application doesn't have that access - but that is not to say that checking it's 32bit status is not a good thing - and if AIF checking is a way of acchieving this *fine* (not having an AIF however *does not* mean an application is *not* 32bit ready). I would caution that the reality is a lot of code out their *doesn't* have AIF headers and never will. Given Paul Stewarts consiliatory article elsewhere it is rather saddening to hear you describe "RISC OS 5 looking plain stupid". I don't recall making such a remark about RO Select and I'd also point out that I have already (twice on this thread) said I had no problem in principle with AIF checking.