Hi Geo,
First of all, great progress with the pilMCU so far, I hope the EEPROM
continues to work and you can move on to the next step.
A small suggestion - please put big image files on some site (imgur etc) and
attach - it would be easier, downloading large email file takes time (I don't
use
On November 25, 2014 at 11:19 AM Kuba Tyszko k...@lbl.pl wrote:
is this actually the whole picolisp converted somehow to a dedicated CPU
running on FPGA, or is that an actual CPU emulated (say some kind of ARM),
and picolisp compiled for that CPU ?
It is a new CPU.
I'm just trying to
Hi Kuba!
I see that Jakob and Alex already covered most of your inquiry, but i'll just
answer you too ;)
First of all, great progress with the pilMCU so far, I hope the EEPROM
continues to work and you can move on to the next step.
Thanks!! and yes, i utilized one push button so that every
Hello Pierpaolo Bernardi olopie...@gmail.com :-)
You are now subscribed
picolisp@software-lab.de
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hello.
I am having some trouble working with Strings or Transient Symbols. (I'll call
them strings for now.)
Consider this string:
^(a+)\)
In picoLisp, I must enter that as:
\^(a+)\\)
See, the escaping syntax is a pretty heavy burden for the types of strings I
work with...
..and I just got to the same exact point, compiled minipicolisp for
stm32f4-discovery,
(same modifications, reduced allocation size, removed argc/argv etc).
semihosting output redirection:
Open On-Chip Debugger 0.8.0 (2014-11-25-23:38)
Licensed under GNU GPL v2
For bug reports, read
Hi Dave,
I am having some trouble working with Strings or Transient Symbols.
(I'll call them strings for now.)
...
^(a+)\)
In picoLisp, I must enter that as:
\^(a+)\\)
That's right. This is the syntax of the PicoLisp reader.
See, the escaping syntax is a pretty heavy burden
