Might be nice to keep as much of that as possible with an android ndk/jni
approach also. For example for C file io one could do something like:
http://stackoverflow.com/questions/1992953/file-operations-in-android-ndk
Android picolisp would definitely need to coexist with java classes, no way
Hi Jakob,
> It's perfect for bootstrapping. That it is.
Well, not only that. It is the only way to get PicoLisp running on
non-POSIX systems, and an easy way to build a non-browser GUI. It has
more features than miniPicoLisp (bignums, utf-8, networking, tasks,
timers, call, piped-I/O) plus access
On Thu, Jul 07, 2011 at 03:33:03PM +0200, Alexander Burger wrote:
>
> Yeah, I always felt that Ersatz (or Java in general) is "not the right
> thing".
It's perfect for bootstrapping. That it is.
// Jakob
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi Doug,
> Ok, here's a plan for :-) a real Android picolisp ... start by taking
Indeed. A fascinating idea! I never thought about a non-Java version for
Android.
> a version of picolisp, and begin cutting it back by dropping everything
> ndk c/c++ headers do not support. So, the idea would be
Hi Doug,
you've been pretty busy. :)
cheering everybody on...
/e
On Thu, Jul 7, 2011 at 4:43 PM, Doug Snead wrote:
> http://developer.android.com/sdk/ndk/overview.html :
> "Typical good candidates for the NDK are self-contained, CPU-intensive
> operations that don't allocate much memory, such
http://developer.android.com/sdk/ndk/overview.html :
"Typical good candidates for the NDK are self-contained, CPU-intensive
operations that don't allocate much memory, such as signal processing, physics
simulation, and so on."
Ok, here's a plan for :-) a real Android picolisp ... start by taking
