[Aldor-l] Portability

[pip88nl at gmail.com]

On Sat, Aug 16, 2008 at 12:27:04PM -0400, Stephen Watt wrote:
> So, for example,  it may be that we will never use again a platform
> with a severely broken C compiler so that CC_no_void_pointer and
> CC_no_token_paste and CC_no_empty_file are obsolete.

They are possibly obsolete and possibly baggage, but they are abstracted
away, so does it hurt? The token paste is being used by librona, so that
already requires a compiler that supports it. The no empty file
requirement is definitely baggage. It makes files ugly (ThatsAll). The
no-void-pointer is no baggage, really. It's hard to say what is and what
is not obsolete.

> On the other hand, segmented architectures keep coming back in
> different guises.  We now have NUMA, and the C standard does not
> require that pointers be cannonical, so I would fear that we have to
> keep the pointer cannonicalization but restrict its use to low-level
> code, e.g. the garbage collector or EQ hashtables.

NUMA.. Is there any way someone can test aldor on NUMA?

By the way, I started a table of portability issues on my website:
http://xinutec.org/~pippijn/en/projects_aldor_porting.xhtml
I wanted to do it on the algebraist wiki, but it doesn't support the
mediawiki formatting I wanted (coloured cells in tables) or maybe I just
didn't find the origo way to do it.

Pippijn
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://mail.aldor.org/pipermail/aldor-l_aldor.org/attachments/20080816/26891606/attachment-0002.bin>