> Android is definitely not unix at all.
And anyone producing cross-platform applications is going to greatly
appreciate being able to check 'android, 'ios, 'nativeclient, et cetera;
rather than check 'unix and then access a secondary egg or their own
custom code to differentiate between what
I've assigned a number to each test (sequentially from 101 to 158) and
added the TEST variable. In this way you can select a single test to
be executed. For example:
# make PLATFORM=macosx PREFIX=/tmp/chicken check TEST=102
make -f ./Makefile.macosx CONFIG= check
cd tests; sh runtests.sh
=
On Feb 21 2013, Jörg F. Wittenberger wrote:
Somehow I can't verify that my type declarations are actually
effective.
I've been able to verify that my .types files are not ever consulted.
Using strace I found that the "foo.types" file is searched for in
stat("/usr/lib/chicken/6/foo.types", 0
* Moritz Heidkamp [130221 17:49]:
> Christian Kellermann writes:
> > Probably android for both, since android does not come with all
> > posix things. pthreads for example.
>
> That's not quite true, is it? See
> https://android.googlesource.com/platform/prebuilts/ndk/+/master/8/platforms/androi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/22/2013 08:02 AM, Moritz Heidkamp wrote:
> I think this kind of mechanism is something we should have in order to
> provide proper support for custom read syntax and to make SRFI 10 syntax
> behave as expected. Let me know if you have any sugges
Fellow Chickeneers,
find attached a patch which allows user code to hook into the quasiquote
code expander. "What good can come from that?" you might ask. Let me
elaborate! As you know, Chicken supports custom reader extensions via
set-read-syntax! and friends. This is all fine unless you try to a
