Re: Bugreport - (sect) passed list with NIL as element

2022-03-29 Thread Jean-Christophe Helary
> On Mar 30, 2022, at 0:29, Alexander Burger wrote: > > As Pil64 is obsolete anyway, I strongly recommend to migrate to Pil64. ??? -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/ -- UNSUBSCRIBE: mailto:picolisp@softw

Re: Bugreport - (sect) passed list with NIL as element

2022-03-29 Thread Alexander Burger
On Tue, Mar 29, 2022 at 05:29:02PM +0200, Alexander Burger wrote: > As Pil64 is obsolete anyway, I strongly recommend to migrate to Pil64. Oops! Of course I wanted to say "... migrate to Pil21". -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Bugreport - (sect) passed list with NIL as element

2022-03-29 Thread Alexander Burger
Hi Morris, > I might have encountered a bug related to > (sect) and it's handling of NIL as element of > the first passed list: > ... > A possibly related bug can be found with (diff): > ... Thanks for finding these bugs! I was not aware of them. > I encountered this behavior on version 20.7.4

Bugreport - (sect) passed list with NIL as element

2022-03-29 Thread Morris
Hi Alex, I might have encountered a bug related to (sect) and it's handling of NIL as element of the first passed list: : (sect (list NIL) NIL) -> (NIL) # expected () It is not dependent on the second argument being the empty list: : (sect (list 1 2 NIL 4) (list 2 3 4)) -> (2 NIL 4) # expect