warning in io.c

2010-10-06 Thread Edwin Eyan Moragas
Hi all, compiling picolisp gives me this warning: io.c: In function =91doEcho=92: io.c:2161: warning: =91op=92 may be used uninitialized in this function my problem is that i can't find where `op is defined. any help would be appreciated. best, /e -- UNSUBSCRIBE:

Re: warning in io.c

2010-10-06 Thread Alexander Burger
Hi Edwin, io.c:2161: warning: =91op=92 may be used uninitialized in this function my problem is that i can't find where `op is defined. any help would be appreciated. Well, 'op' is declared in that line (2161), and initialized in line 2176. The C compiler is wrong with its warning. 'op' is

Re: picolisp in java

2010-10-06 Thread Alexander Burger
Hi Tomas, For production system, all these functions should be coded in Java instead of lisp, but it vas a great learning exercise this way, especially in the context of argument evaluation and shallow binding maintenance. T What I actually like most about wl is the Java FFI which is very

Re: upload form

2010-10-06 Thread Tomas Hlavaty
Hi Alex, Instead of the alerts, you could also put a +TextField onto the original form to display proper messages, ok, now I have the script below but the question is how do I get hold of the uploaded files, those that were dropped? Also, it seems to be uploading only one file even if I drop

Re: picolisp in java

2010-10-06 Thread Tomas Hlavaty
Hi Alex, Perhaps 'fork' can be simulated by copying all runtime variables to a thread? not sure whether that's enough. The semantics is completely different, what about open files and so on? Is it necessary to go that far in terms of compatibility? Cheers, Tomas -- UNSUBSCRIBE: