[Scummvm-devel] Re: [Scummvm-cvs-logs] SF.net SVN: scummvm:  scummvm/trunk/engines/sky
max at quendi.de
Wed Apr 12 09:05:05 CEST 2006
Am 12.04.2006 um 17:47 schrieb Alban Bedel:
> On Thu, 13 Apr 2006 00:54:16 +1000
> Jonathan Gray <jsg at goblin.cx> wrote:
>> This a libc thing, not a compiler thing.
<sigh>. I guess I'll have to run my mails past a team of lawyers,
spec experts and other consultants in the future before trying to
mail here ;-).
Yes, it's a library thing. The compiler and the library are both
parts of the C99 spec. I.e. to comply to the C99 spec, both the
compiler and the library have to be brought up to speed. In this
particular case, it would indeed be possible for a non-C99 compiler
to have a libc that supports that part of the C99 spec.
Still, there are systems that don't support C99 (fully, at least).
MSVC comes to mind as a typical example. Older GCC versions / glibc
versions, too. Older libc versions on every system out there, in
fact. C lib implementation for many embedded devices. Possibly the C
libs for various of our small device targets, I can't check all of them.
>> I'd be interested to hear of any platforms that don't support
>> it, just out of general interest...
> Me too. BTW nothing prevent defining the missing part yourself.
> IMHO that's
> the best way to go: stick to the current standard and fix the
> broken systems
> with your own headers/definitons (as opposed to always defining
> your own
> stuff and/or using countless #ifdef in the code).
> That way any complying (or close enouth) environement (ie the
> majority) just
> work out of the box, broken or not up-to-date environements would
> need some
> fixes anyway.
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> that extends applications into web and mobile media. Attend the
> live webcast
> and join the prime developer group breaking into this new coding
> Scummvm-devel mailing list
> Scummvm-devel at lists.sourceforge.net
More information about the Scummvm-devel