26/32bit Acorn C/C++ Tools and OSLib

[TIMMERMANS ANDRE]

> -----Original Message-----
> From:	John Tytgat [SMTP:John.Tytgat at aaug.net]
> Sent:	Wednesday, October 30, 2002 4:03 PM
> To:	oslib-user at compton.nu
> Subject:	Re: 26/32bit Acorn C/C++ Tools and OSLib
> 
> In message <5f4c928d4b.Tony at mk-net.demon.co.uk>
>           Tony van der Hoff <tony at mk-net.demon.co.uk> wrote:
> 
> > On 30 Oct 2002, in message <2c708f8d4b.Jo at hobbes.riscos.be>,
> > John Tytgat <John.Tytgat at aaug.net> wrote:
> > 
> > > Is someone busy with patches to make OSLib in SourceForge compilable with
> > > the new 26/32bit Acorn C/C++ Tools from Castle ? I think the biggest
> > > problem is Tools.Yacc as its C style is no longer accepted.
> > 
> > Well, not me :-(
> > 
> > I intend to purchase the new tools, but as I am busy with other things, I
> > have not yet done so. I was therefore not aware that this presented a
> > problem.
> 
> The only problem I saw so far (and then didn't continue to use the 26/32bit
> tools) that is much more picky on function defintions without return type,
> and using functions before they have been declared etc.  I thought that
> I should have been able to get around it by using flags like -pcc but
> that didn't help (caused other problems).  :-(
> 
If you are using the new tools, I think there is a -c90
mode to revert to the old c90 standard instead of the c99 one.

So far my main complain with c99 on my own projects is the warnings
about implicit conversions of signed integers given as hex
in the range [0x8000000,0xffffffff].

André