That makes sense I guess.
Has anyone compiled either of them for the Zaurus?
Is anyone using something else to do spell check in xemacs?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]
As much as I can confirm is they are both ARM friendly.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=114944\"][{POST_SNAPBACK}][/a][/div]
Sorry for my ignorance but do you mean that the binary is all ready compiled with ARM support, or they are easy to compile with ARM support?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=115477\"][{POST_SNAPBACK}][/a][/div]
Some short sighted programming practices assume that software will...
1. Only run on Linux and not other Posix based systems.
2. Only run on i386 or some specific architecture and may...
i. Use assembler instructions for performance without providing a non optimised version using plain C/C++ or whatever.
ii. Not explicitely cast certain types in C where differences in the architecture or compiler implementation either exists or is traditional. It is not strictly defined in the gcc specificatioin if declaring a value as char alone specifies a signed char or an unsigned char, i386 defaults to signed whereas ARM defaults to unsigned. see [a href=\"http://www.arm.linux.org.uk/docs/faqs/signedchar.php]http://www.arm.linux.org.uk/docs/faqs/signedchar.php[/url] for an example.
So ARM friendly I class as satisfying point 2, ispell and aspell will also compile on non Linux systems without too much 'jiggery-pokery' too
- Andy