> > The C standard states that char should be either signed char or unsigned
> > char.
> 
>   The only concern I have is backward-compability. I mean if someone's
> program relies the default sign char, will this change breaks his code?

>From a standards perspective the code was already broken. But yes - it
would.

A lot of 8bit processors are much better at unsigned char (and 16bit
ones too) so I'm for the change. I already have to cover unsigned
default char on non Z80 platforms.

Alan


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user

Reply via email to