[M3devel] thread local storage, but in C pieces of runtime... (jay, tony?)

[Dragiša Durić]

We are talking POSIX here. There are same chances for #define to change behavior of your C as are to change binding through EXTERNAL.

In 90s, when I did port of pm3 to LINUX_ALPHA, most problems I met were in C code, due to it's non-portability to RISC, 64bit, big-endian machine.

--
Dragiša Durić
dragisha at m3w.org



On May 10, 2013, at 6:56 PM, Jay K wrote:

> It is in C for portability. Like everything else.
>  
>  
> Otherwise you have to duplicate the C headers in Modula-3, and they end up being system specific because there are too many ways to turn the portable C source interface into non-portable ABI -- #defines, #pragmas, etc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20130510/80f0126f/attachment-0002.html>