OSLib Namespace for C++

[David Bryan]

In message <200006051841.LAA28651 at purple.trimedia.sv.sc.philips.com>
          "Jonathan Coxhead" <jonathan at doves.demon.co.uk> wrote:

> The exception is a small number of cases where SWI's have been
> split because of different  argument typing: e g
> 
>       extern os_error *xwimp_send_message_to_window
>       (
>          wimp_event_no  event,
>          wimp_message  *message,
>          wimp_w         to_w,
>          wimp_i         to_i,
>          wimp_t        *to_t
>       );
> 
> could become
> 
>       extern os_error *xwimp_send_message
>       (
>          wimp_event_no  event,
>          wimp_message  *message,
>          wimp_w         to_w,
>          wimp_i         to_i,
>          wimp_t        *to_t
>       );
> 
> under which name it overloads the other function with the same name,
> 
>       extern os_error *xwimp_send_message
>       (
>          wimp_event_no  event,
>          wimp_message  *message,
>          wimp_t         to
>       );
> 
> where the 2 are distinguished by the argument types.
> 
>    This is fun, but not incredibly useful, it seems to me.

This could be added simply to OSLib.  Just leave the two
xwimp_send_message function names to get mangled.  Put both CFront
and GCC style mangled functions into to the object library.  Of
course, the object library still becomes out of date, when a
mangling algorithm changes.

-- 
David Bryan