[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-hackers] Feature request: make cond more resilient against misu
From: |
Jörg F . Wittenberger |
Subject: |
[Chicken-hackers] Feature request: make cond more resilient against misuse |
Date: |
05 Apr 2018 12:35:14 +0200 |
Hi all,
admitt this is a case of garbage-in-garbage out.
A `cond` (or `case`) expression with an `else` branch behaves odd when an
empty sequence of expression is given in the `else` branch: it results in
an unbound variable "else" at runtime.
Attached a test case. Try
$ csc unboundvariableelse.scm
$ ./unboundvariableelse
Best
/Jörg
unboundvariableelse.scm
Description: unboundvariableelse.scm
- [Chicken-hackers] Feature request: make cond more resilient against misuse,
Jörg F . Wittenberger <=