Read sprite info/size

[Stewart Brodie]

In message <69ccc6424b.Tony at mk-net.demon.co.uk>
          Tony van der Hoff <tony at mk-net.demon.co.uk> wrote:

> On 6 Jun 2002, in message <ee1389424b.philip at philipnet.com>,
> Philip Ludlam <philip at philipnet.com> wrote:
> 
> > Dear All/Tony,
> > 
> > SWI Wimp_SpriteOp read sprite info (reason code 40) goes under the guise
> > of WimpSpriteOp_ReadSpriteSize in OSLib.
> > Is there a reason for Size rather than Info?
> > 
> I have no idea; this pre-dates my involvement in OSLib. As it's consistent
> with OSSpriteOp_ReadSpriteSize, it's unlikely to be just an oversight. 
> 
> I hope Jonathan is still monitoring these groups (if only to keep us on the
> straight and narrow ;-), and maybe he can give the reason.
> 
> I guess it's unlikely to get changed, whatever the reason, and I'm not
> sure that this justifies a new, synonymous call, but I'd be happy to add a
> comment to the help text.

There are one or two cases where API names do not match what ended up in the
PRMs - and it's not just in OSLib that his happens either.  Some of our other
libraries suffer from this too, so I suppose it could just be a case of the
names being changed in the specifications (and hence manuals) at a later date
at a review, but the software not keeping up.

-- 
Stewart Brodie, Senior Software Engineer    (Views expressed are my own and
Pace Micro Technology PLC                   not those of my employer)
645 Newmarket Road
Cambridge, CB5 8PB, United Kingdom         WWW: http://www.pacemicro.com/