Re: More DrRacket binding arrow woes

There are bugs in DrRacket's handling of the automatic-zo compilation
mechanism that I know about and have been trying to find time to fix.
With the current buggy state, you should always be able to get to a
non-buggy use if you do a "raco make x.rkt" in the shell (I think).
Or, if you disable DrRacket's automatic zo creation, that should also
avoid this problem (but then you have to manage the .zo files
yourself, of course, and racket's default settings can also lead to
confusing behavior when zo files are out of date.)

Glad you got it fixed!

Robby


On Sat, May 7, 2016 at 12:21 PM, Alexis King <[email protected]> wrote:
>> So, the bindings are fine, and the syntax-original? property is fine. Is the source location good, including the `syntax-source` field?
>>
>> I had a similar issue once, and it turned out that it was because the `syntax-source` part of the source location was wrong. I had been using things like `(input-port-append (open-input-string ....) ....)`, which were resulting in `syntax-source` fields of `'string` for some of the syntax objects. So that's something silly that can happen.
>
> Yup, this seems to have been the problem. Interestingly enough, I had
> thought of this before, but faking out the source field with what
> appeared to be the proper value didn’t seem to work. I’m not entirely
> sure why, but Robby’s suggestion helped track down the issue, and based
> on the behavior I saw, it seems like it might be due to bad caching of a
> .zo file that for some reason seemed to be sporadically picked up when
> running the expander in different ways (Check Syntax, Macro Stepper,
> just running the thing and printing things out).
>
> I’m not really sure about why I was having difficulty getting those
> changes to reload before, but that’s a separate issue. It would be a
> little nice to mention the complete list of fields that DrRacket looks
> at before drawing arrows, given that I had no idea which things I needed
> to check. At least having a checklist of properties would help with
> that, and the logging idea would be helpful, too.
>
> Thanks to both of you!

-- 
You received this message because you are subscribed to the Google Groups "Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
For more options, visit https://groups.google.com/d/optout.