technoblogy / ulisp-arm

A version of the Lisp programming language for ARM-based boards.

ulisp-arm

A version of the Lisp programming language for boards based on the ARM processor:

• Arduino Zero and MKRZero.
• Arduino Uno R4 Minima and WiFi.
• Adafruit ItsyBitsy M0, Feather M0, and Gemma M0.
• Adafruit Metro M4, ItsyBitsy M4, Feather M4, and Grand Central M4.
• Adafruit PyBadge and PyGamer.
• Adafruit CLUE and ItsyBitsy nRF52840.
• Raspberry Pi Pico and Raspberry Pi Pico W.
• BBC Micro Bit.
• Maxim MAX32620FTHR.
• Teensy 4.0/4.1.

The "-comments" version is identical but includes comprehensive comments.

For more information see: http://www.ulisp.com/

ulisp-arm's Issues

Random fails with float argument

> (random 2.0)
Error: 'random' argument is not a number: 2.0

uLisp: New target: Infineon XMC1100 bootkit

Hi David, greetings!

Many thanks for uLisp! I enjoyed reading the uLisp source code and its
references. I have an Infineon XMC1100 boot kit lying around. I wanted
to make a uLisp project for it and make it available. How do you think
I should proceed?

o) I notice that you have a ulisp-stm32 project available. Should I
make a ulisp-xmc for example?

o) OR would it be better to add the relevant conditional compilation
sections and add support for the core alongside your ulisp-arm
project?

Raman

Characters incorrectly converted to strings

If you convert a character to a string with the function string the resulting string may be corrupt.

For example:

>(defvar a (concatenate 'string "Hello" (string #\!)))
a

> a
"Hello!"

> (char a 5)
Error: 'char' index out of range

(lambda x x) loops forever

I think a more sensible behaviour is possible. Either error or do like in scheme (bind x to the list of arguments):

((lambda x x) 1 2 3))
=> (1 2 3)

expt should be able to raise negative numbers to integer powers

> (expt -2 2)
4

> (expt -2.0 2)
Error: ‘expt’ invalid result

Thanks to Fausto Saporito for reporting this.

Can't pass user-defined symbols to apply

The first argument to apply can't be something like:

(defun my (x y) (+ x y))
(defvar handlers '(my))
(apply (first handlers) '(0 1)) 
Error: not valid here: my

Note that it affects all platforms, and also affects other functions that take a function argument, such as funcall, mapc, mapcar, sort, etc.

Thanks to @jurov for reporting this.

Is it work without arduino?

Hello,

I don't use Arduino tools. Can it be compiled with just Pico SDK?

The or special form evaluates its argument twice

For example:

> (let ((x 0)) (or (incf x)) x)
2

Thanks to Max-Gerd Retzlaff for finding this.

Calling 'pinmode' with a numeric argument behaves incorrectly

Calling 'pinmode' with a numeric argument does not set the mode of the pin correctly.

print no longer prints readably

> (print "Hello")

hello

let and let* cause a crash if the first argument isn't a list

For example:

(let 24 24)

Negative index to nth should give an error

> (nth -1 '(a b c))
nil

Incorrect result when 'or' has a quoted argument

Demonstration:

> (or 'a 'b)
Error: 'a' undefined

Using return outside a block causes odd behaviour

Calling return outside loop, dotimes, or dolist causes subsequent loops to fail. For example:

(defun test ()
  (dotimes (x 6) (princ x))
  (return 67))

It works the first time but fails the second:

> (test)
012345
67

> (test)
0
67

Will be fixed next release. Thanks to Brian O'Dell for reporting this.

A malformed array definition can crash uLisp

For example:

> #2A((1 2) 3 4 5)

Workaround: don't do this.

Problem saving large images to flash

Images larger than 8192 objects are corrupted when saving them to flash with save-image.

ARM uLisp doesn't work on Teensy 4.0/4.1

Due to a typo. See:

http://forum.ulisp.com/t/hanging-ulisp-with-unknown-symbol-on-teensy/743

Thanks to Aeneas for reporting this.

with-spi divider parameter doesn't work

On ARM platforms the SPI divider parameter should allow a range of 1 to 255. Thanks to Ronny Suy for reporting this.

Sometimes a return statement never returns

If the expression in a return statement calls a function that itself uses a return statement, the first return statement never returns. For example:

(defun tst (x)
  (loop
   (return (fun x))))

(defun fun (y)
  (loop
   (return (car y))))

then calling:

(tst '(a b))

should return a, but instead hangs up.

A workaround is to assign the result to a temporary variable, and then return that:

(defun tst (x)
  (loop
   (let ((val (fun x)))
     (return val))))

(defun fun (y)
  (loop
   (return (car y))))

So now, as expected:

> (tst '(a b))
a

Length of one-dimensional array returns a negative size

> (defvar a (make-array 10 :initial-element 1))
a

> a
#(1 1 1 1 1 1 1 1 1 1)

> (length a)
-10

Thanks to Fausto Saporito for reporting this.

Variable undefined error

Under some circumstances uLisp 2.7 and 2.7b can give a "variable undefined" error while executing a program.

for-millis gives an error if the argument isn't an integer

For example:

> (defvar n 1000)
n

> (for-millis (n) (print "Hello"))
Error: Not a number

Will be fixed next release. Thanks to Pascal Lorenz for reporting this.

Bug in floating-point print

Some exact multiples of 10 are printed incorrectly. For example:

> 70.0
7.0

Error in format printing a nil list

This should just print nil:

> (format t "~{~a~}" nil)

    "~{~a~}"
        ^
Error: 'format' missing argument

Function corrupted by 'makunbound'

If you define a function by reading it from a string and then eval it, and them remove it with makunbound, other functions get removed:

(defun test () (eval (read-from-string "(defun bob (y) (* y y))")))
(test)

> (globals)
(bob test)

> (makunbound 'bob)
bob

> (globals)
()

This only seems to happen if the function was defined by reading it from a string.

Thanks to Klaus Fuerth for reporting this.

Serious problem running on Grand Central

There is a mismatch between the workspace definition for the Adafruit Grand Central M4 Express on the one hand and the definitions used to detect which keywords should be included. Because the final entries in the lookup table are not included unconditionally, that means the reader can run right off the end of the lookup table, locking up the processor.

Fortunately, the fix seems to be simple - instead of defining CPU_ATSAMD51P20 for the Grand Central, define it with CPU_ATSAMD51. This is safe - the Adafruit SAMD core defines all the relevant constants regardless of the MCU being used.

I noticed this because a similar error caused a failure to build in my altered version.

mapcan gives error if last item is a dotted list

This should work:

(mapcan (lambda (x) x) '(nil (2) (3 . 4)))

Thanks to Herbert Snorrason for reporting this.

symbolp should give t with nil

See technoblogy/ulisp-esp#45.

funcall and apply shouldn't accept special forms

For example:

(funcall let)

causes a crash.

Error reading some character constants

These three:

(print #\()
(print #\))
(print #\ )

Thanks Aeneas.

Error in anonymous function gives corrupted error message

For example:

20479> ((lambda (x) (* x x)) 3 3)
Error: 'ei*yyx' too many arguments

Adafruit Feather M4 Express analog read range extension to 20 (A6)

Thank you for beautiful uLisp. Adafruit Feather M4 Express function analogread argument is limited from 14 (A0) to 19 (A5) ports. This range match external analog inputs for the board. But there is internal, not exposed A6 analog input which provides reading for battery voltage. This value is quite usable and it make sense to extend analogread function's range from 14 (A0) to 20 (A6).
SNC.

make-array dimensions don't accept a one-element list

> (make-array '(2))
Error: 'make-array' argument is not an integer: nil

Thanks Aeneas!

Cannot compile for BBC microbit

Following these instructions: http://www.ulisp.com/show?2672#example_programs
I get the following error at line 1197 when I try to upload the ulisp-arm code to my BBC microbit: 'else' without a previous 'if'
The error is in the definition of serialbegin, and I guess it is because _VARIANT_BBC_MICROBIT_ is defined, and ARDUINO_SAM_DUE is not defined, so the precompiler skips over the previous if statements.

uLisp crashes with (if) or (cond t)

(if) or (cond t) crashes Lisp on some platforms. Thanks to Aeneas for reporting this.

FlashIAPBlockDevice.h: No such file or directory

Trying to compile in the Arduino IDE for Reaspbery Pi Pico. I'm running Arduino IDE 1.8.16 and have re-installed a couple times and looked for some mbed library that must not be included with the default install but can't find anything. Any ideas?
I've compiled this for Feather M4 Express with an SD Card but that case didn't encounter the need for this file/library.

GC bug?

I'm not 100% sure, but I think I found a potential problem around https://github.com/technoblogy/ulisp-arm/blob/master/ulisp-arm.ino#L4916.

If a GC is triggered in the val in that line, very strange things happen. The "form" is put into the freelist, and because some pointers to it are held, part of the freelist ends up in the args. I'm not 100% sure this applies to the stock version, but on my heavily hacked-on test I can trigger it with running this http://www.ulisp.com/list?21S2

Characters with high bit set should print and read consistently

See:

http://forum.ulisp.com/t/bytes-are-not-characters/742/10.

Thanks to Herbert Snorrason for raising this.

Dotted pairs crash list functions

Many of the functions that take a list argument cause a crash if you provide a list ending in a dotted pair.

For example:

(length '(2 3 . 4))

make-array doesn't check indices individually

(aref (make-array '(3 2) :initial-element 'A) 0 2)

should give an error. Thanks Aeneas!

First character of SD card filenames is truncated

For example:

(with-sd-card (str "Greeting.txt" 2)
  (print "Hello" str))

will create a file "REETING.TXT" on the SD card.

Negative index to subseq should give an error

Instead it returns a spurious result:

> (subseq "ulisp" -1 2)
"sul"

GC during (sort) occasionally causes corruption

Bit arrays don't work without an :initial-value

For the moment please define bit arrays with, for example:

(defvar a (make-array 100 :element-type 'bit :initial-element 0))

(or :initial-element 1). This will be fixed next release.

Corruption using with-output-to-string

If a garbage collection occurs during execution of a with-output-to-string form the result string may be corrupted.

This will be fixed in the next release. Thanks to Max-Gerd Retzlaff for reporting this.

Missing arguments to special forms should give an error

The special forms should signal an error in all cases of malformed forms:

(dotimes ())
(dolist ())
(let)
(let*)
(with-output-to-string)

Thanks to @Goheeca for reporting this.

#' not ignored before a bracketed form

It was intended that

#'(form)

would be treated as equivalent to

(form)

for compatibility with Common Lisp, but this causes incorrect parsing.

AR_INTERNAL not supported on Adafruit SAMD21 boards

uLisp gives a compile error on Adafruit SAMD21 boards: AR_INTERNAL not defined.

It's equivalent to AR_INTERNAL2V23 and so can be removed. Thanks to Herbert Snorrason for reporting this.

cond gives error if test clause omitted

Example:

(defun test (n)
  (cond
   ((oddp n) n)
   ((list n))))

(test 2) gives an error. Workaround: include a t for the final clause:

(defun test (n)
  (cond
   ((oddp n) n)
   (t (list n))))

Spurious character from serial port

On some platforms I'm getting a spurious character appearing in the Serial Monitor on starting uLisp; for example, on the Arduino Due:

This is generated by code which is effectively:

Serial.begin(9600);
Serial.println(PSTR("uLisp 2.2 "));

Can anyone suggest where the spurious character is coming from and how I can get rid of it?