Hi Tomas,
> >> > java wlErsatzLisp Pil32Pil64
> >> > +---
> >> >(fibo 22) | 250.19 0.0150.016
> >> >(fibo 23) | 450.25 0.0260.024
> >> >(fibo 24) | 690.36 0.
Hi Alex,
>> > java wlErsatzLisp Pil32Pil64
>> > +---
>> >(fibo 22) | 250.19 0.0150.016
>> >(fibo 23) | 450.25 0.0260.024
>> >(fibo 24) | 690.36 0.0410.03
Hi Edwin,
> by the way, thank you for releasing this in the wild. your java
> implementation gave me a better understanding how picolisp works under
> the hood.
you are welcome;-)
BTW, thanks Alex for mentioning the build problem. I fixed it now so
you can git pull again.
Cheers,
Tomas
--
U
Hi Tomas,
On Thu, Oct 14, 2010 at 1:43 AM, Tomas Hlavaty wrote:
>
> In that email, I just wanted to say that I implemented some functions
> directly in Java and that speeds up the fibo benchmark significantly.
> For getting better picture about interpretation overhead, there are now
> three versi
Hi all,
oops oops! No problem with the mail archive. I sent it to myself:-(
Sorry for the confusion, must have been too tired.
>> However, what disturbs me more: Where does the above quote come from?
>> I didn't get that mail. Anybody? Did you really send it? It seems
>> also not to be in the
On Wed, Oct 13, 2010 at 4:07 PM, Alexander Burger wrote:
> Hi Tomas,
>
>> > If you get the latest wl code (git pull), you'll see even a pure java
>> > 'fibo.' function for comparison and getting an idea of the overhead
>> > caused by interpretation.
>
> However, what disturbs me more: Where does t
Hi Tomas,
> > If you get the latest wl code (git pull), you'll see even a pure java
> > 'fibo.' function for comparison and getting an idea of the overhead
> > caused by interpretation.
Yeah, I know that very well. Did a lot of 'fibo' tests during the last
30 years ;-) Here, locally, I see that a
> If you get the latest wl code (git pull), you'll see even a pure java
> 'fibo.' function for comparison and getting an idea of the overhead
> caused by interpretation.
Oops, forgot to push. Now in the repo.
Cheers,
Tomas
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
Hi Alex,
Yes, building a new JAR made it. Thanks!
/Jon
> Hi Jon,
>
>> Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad
>> version number in .class file
>
> It seems that this error occurs if the java runtime version is older
> than that of the classes in the JAR file.
>
>>
Hi Jon,
> Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad
> version number in .class file
It seems that this error occurs if the java runtime version is older
than that of the classes in the JAR file.
> $ java -version
> java version "1.5.0_24"
I have here:
$ java -ve
Hi Alex,
> after two weekends of fiddling, I decided to release a first - very
> rudimentary - version of Ersatz Lisp, the Java version of PicoLisp.
great, thank you!
Tomas
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
Hi,
I tried to run ersatz/picolisp on my Mac, but it didn't turn out too well:
$ ersatz/picolisp
Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad
version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defin
It will be very interesting to see what this will lead to.
Having a Java version might help PL a lot on the popularity front, it
should completely bypass the catch 22 problem of low interest due to
to few libraries and few libraries due to low interest.
/Henrik
On Sun, Oct 10, 2010 at 3:00 PM,
Hi all,
after two weekends of fiddling, I decided to release a first - very
rudimentary - version of Ersatz Lisp, the Java version of PicoLisp.
See ersatz/README.
It is not really usable yet, because not more then just a hand full of
functions are implemented. But most essential data structures
On 10/06/2010 10:04 PM, Tomas Hlavaty wrote:
> 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 o
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: mailto:pi
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
Hi Alex,
> btw, the strategy of deriving _all_ flow functions from 'loop' is very
> elegant!
thanks! It is indeed elegant and very inefficient;-)
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
Hi Tomas,
btw, the strategy of deriving _all_ flow functions from 'loop' is very
elegant!
Cheers,
- Alex
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
Hi Alex,
> For example, even simple 'if' is implemented as a picolisp fexpr:
>
>(de if (C . L)
> (loop
> (T C (up. '@ @) (eval (car L) 1))
> (T T (run (cdr L) 1)) ) )
one of the significant factors that are slowing it down is all these
environment lookups like the 'up.
Hi Jon,
> I'm just curious, what does that 'up.' do? I can't find it in the
> PicoLisp ref.
'up.' is an internal function implemented in directly in Java. It was
needed as a functional equivalent to 'up' because I needed something
that would expect quoted agruments. 'up' is not programmable.
/
http://www.software-lab.de/doc/refU.html#up
On Tue, Oct 5, 2010 at 2:14 PM, Jon Kleiser wrote=
:
> Hi Tomas,
>
> On 10/4/10 7:27 PM, Tomas Hlavaty wrote:
> ..
>>
>> For example, even simple 'if' is implemented as a picolisp fexpr:
>>
>> =A0 (de if (C . L)
>> =A0 =A0 =A0(loop
>> =A0 =A0 =A0 =A0 (T
Hi Tomas,
On 10/4/10 7:27 PM, Tomas Hlavaty wrote:
..
For example, even simple 'if' is implemented as a picolisp fexpr:
(de if (C . L)
(loop
(T C (up. '@ @) (eval (car L) 1))
(T T (run (cdr L) 1)) ) )
..
I'm just curious, what does that 'up.' do? I can't find it in
Hi Alex,
>> Did you type anything into the text field? The example is very
>> simplistic so it expects an integer value in the text field when you
>
> Yes, as I wrote in my previous mail, that field doesn't respond. That
> is, it doesn't accept any keystrokes. But now it occurs to me that
> these
Hi Tomas,
> Just to note, you are also measuring startup time of the JVM which might
> be considerably slow compared to picolisp. In that sense, your
> ErsatzLisp might have unfavourable timings in regard to pure
> interpretation.
Yes, I'm aware of that. Still, if I just put (bye) into a file 'y
Hi Alex,
> and then did
>
>$ time cat x |java wl
ok.
Just to note, you are also measuring startup time of the JVM which might
be considerably slow compared to picolisp. In that sense, your
ErsatzLisp might have unfavourable timings in regard to pure
interpretation.
>> > respond, however, a
Hi Tomas,
> I wasn't aiming for speed with this first version but rather for
> understanding of the underlying concepts, namely how evaluation and
> shallow binding works and creating simple but generic and powerful Java
> FFI. If you have a look at the code, you'll find that only necessary
> min
Hi Alex,
> It runs without problems.
great!
> I'm a little bit surprised, however, that it is so extremely slow.
> How can these huge differences be explained?
I wasn't aiming for speed with this first version but rather for
understanding of the underlying concepts, namely how evaluation and
sh
picolisp in java, in case you want
> to compare with your implementation.
>
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
Hi Tomas,
> I have published my implementation of picolisp in java, in case you want
> to compare with your implementation.
Thanks! Great!
It runs without problems.
I'm a little bit surprised, however, that it is so extremely slow.
When I tried this
(de fibo (N)
30 matches
Mail list logo