Why not check what information is put in *features* by other 
implementations?  If OpenAxiom runs on them, then that should be enough.

Keywords like :X86 and :X86-64 seem common, and this should be easy to 
figure out when building ECL.  :ILP32 or :LP64 might be even more 
informative than that.  Since ECL depends on a C compiler, maybe an 
additional :GCC or :SUNCC or whatever keyword identifying the compiler 
would be useful too.

Clozure CL has target and host endianness and word size information.  
Armed Bear CL will tell you what Java version (1.5 or 1.6) it is running 
on.  Even CLisp (which IIRC compiles to portable bytecode) says 
something like :PC386.

This information is useful, can usually be figured out at build time, 
and is harmless to put in *features*.

Regards.

-DS

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list

Reply via email to