> >
> > There is a protocol_version test in feathers.tcl ... Is this what you mean?
>
> Ah, I suppose so. I couldn't find it so quickly; where is it in the C code?
C_DEBUG_PROTOCOL_VERSION
> What happens when the version is different?
feathers aborts.
felix
On Sun, Nov 25, 2018 at 07:29:57PM +0100, felix.winkelm...@bevuta.com wrote:
> >
> > One thing though; I think we need to add some sort of versioning support
> > to the debugger protocol so when you run feathers to talk to a program
> > compiled with a different version of CHICKEN, this is going
>
> One thing though; I think we need to add some sort of versioning support
> to the debugger protocol so when you run feathers to talk to a program
> compiled with a different version of CHICKEN, this is going to fail.
>
> I think this is a situation we ought to at least detect and warn or
On Sun, Jul 22, 2018 at 11:45:17PM +1200, Evan Hanson wrote:
> Hello hackers,
>
> Here are a few small changes to the debugging backend, to address some
> snags I hit into while working on a program that uses the debugger
> protocol. As the commit message says, they're intended to "simplify the
>
On Thu, Nov 22, 2018 at 11:46:44AM +0100, felix.winkelm...@bevuta.com wrote:
> This patch adds an additional optimization pass to the "lfa2"
> compiler stage, which attempts to remove unnecessary
> boxing and unboxing of floating point numbers. Specifically,
> calls to floating point inline
Hi Peter,
I tested building again with your patch and the warnings are now
gone. Pushed :-)
Moritz
--
bevuta IT GmbH
Marktstrasse 10 | http://www.bevuta.com/ | HRB 62476 AG Cologne
D-50968 Cologne | Tel.: +49 221 282678-0 | CEO: Pablo Beyen
___
