Re: [Chicken-users] invalid encoded numeric literal (was: CHICKEN 4.12.0 rc2 available)

[Claude Marinier]

Hi Evan,

On 2017-02-14, Evan Hanson wrote:

> Thanks for testing the RC, it's appreciated.

Glad to help.

> On 2017-02-13 21:32, Claude Marinier wrote:
> > With current MinGW-w64 and PLATFORM=mingw-msys : builds successfully

> > and checks die with the same error as 4.11.
> >
> >     [panic] invalid encoded numeric literal - execution terminated
> >
> > See http://lists.nongnu.org/archive/html/chicken-users/2016-08/msg00009.html
> >
> > If I am the only one experiencing this error, is it worth pursuing?
>
> You are not the only one -- this is a known issue and something we'd like to
> fix but haven't gotten to yet. Refer to https://bugs.call-cc.org/ticket/1344
> and please feel free to elaborate if you have any details to add.

I am trying to reproduce the error with the intent of poking around. How can I tell 'csc' to keep the generated C?

By the way, right after building, I notice 'csi' behaves oddly.

address@hidden MINGW64 ~/chicken-4.11.1/tests

$ csi

(* 1 2 3 4 5)

(exit)

CHICKEN

(c) 2008-2016, The CHICKEN Team

(c) 2000-2007, Felix L. Winkelmann

Version 4.11.1 ((detached from 4.11.1)) (rev 116f42e)

windows-mingw32-x86-64 [ 64bit manyargs dload ptables ]

compiled 2016-09-12 on waldrop (Linux)

120

address@hidden MINGW64 ~/chicken-4.11.1/tests

$

This is unexpected. It looks like a terminal I/O problem. Is this known?

Thank you.

--

Claude Marinier