Re: [Chicken-users] pp and write ignore keyword-style

2018-11-20 Thread Evan Hanson
Hi Sven, On 2018-11-20 22:51, Sven Hartrumpf wrote: > pp and write (in chicken 5) do not respect the parameter (keyword-style); > Only display respects keyword-style. This behaviour is intentional, for the reasons John describes. Refer to ticket #1332 for specifics about the change:

[Chicken-users] Duplicate symbol errors with functors and -static flag

2018-11-20 Thread Antoine Luciani
Hello, I came across weird duplicate symbol errors while using functors and the -static flag in CHICKEN 5. You can find the full repro here in case my explanation is not clear: https://github.com/antoine1fr/chicken-functor-static-error. Given: * a unit 'a', * a unit 'make-b' that defines a

[Chicken-users] pp and write ignore keyword-style

2018-11-20 Thread Sven Hartrumpf
Hi. pp and write (in chicken 5) do not respect the parameter (keyword-style); Only display respects keyword-style. #;1> (import (chicken pretty-print)) ; loading /usr/local/chicken-5.0.0-x32/lib/chicken/9/chicken.pretty-print.import.so ... #;2> (keyword-style) #:suffix #;3> (write '(arg1: 1))

Re: [Chicken-users] Duplicate symbol errors with functors and -static flag

2018-11-20 Thread Evan Hanson
Hi Antoine, The issue here is the "./" prefix on $(SCHEME_OBJECTS). Your project works fine with just the following change: 3c3 < SOURCE_PREFIX = ./ --- > SOURCE_PREFIX = CHICKEN uses a naive string comparison to deduplicate object files, so "./a.o" and "a.o" are considered to

Re: [Chicken-users] Duplicate symbol errors with functors and -static flag

2018-11-20 Thread Antoine Luciani
On Nov 20, 2018, at 6:59 PM, Evan Hanson wrote: > > Hi Antoine, > > The issue here is the "./" prefix on $(SCHEME_OBJECTS). Your project > works fine with just the following change: > >3c3 >< SOURCE_PREFIX = ./ >--- > SOURCE_PREFIX = > > CHICKEN uses a naive string comparison to

Re: [Chicken-users] pp and write ignore keyword-style

2018-11-20 Thread Sven Hartrumpf
John Cowan wrote on 2018-11-20 16:56: > IMO, `write` should not respect `keyword-style` but use the invariant > syntax `#:foo` for keywords, as that always works, whereas `foo:` > and `:foo` don't. The whole point of `write` is that you can reread > the output with `read` and get something that