Peter Bex scripsit:
> These sound useful, but are they available on, say a system which
> runs on top of Java or another VM? Or would that VM _be_ the "CPU"?
I'll add jvm, clr, and llvm to the list. Such a list is inevitably
open-ended anyhow.
> Also, I propose to add big-endian and little-endian to that list.
I'm not even sure why I left them out, though they belong on a different
list. The JVM and CLR make it impossible to determine (short of native
code) what the underlying byte order is, however, so some systems will
have neither.
> How useful is this? I've seen code that checks if a certain minimum
> version of an implementation is in use, but the precise version isn't
> *that* useful in cond-expand (except maybe in rare cases where only
> that version is known to contain a critical bug which needs to be
> worked around).
That's what I had in mind.
--
Go, and never darken my towels again! John Cowan
--Rufus T. Firefly http://ccil.org/~cowan
_______________________________________________
r6rs-discuss mailing list
[email protected]
http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
