On Jul 25, 2015, at 2:48 PM, Matthew Flatt wrote:
> Do the broken references show up when rendering docs with `raco setup`
> or `raco pkg {install,update}`, or do they show up when running
> `scribble` directly on the ".scrbl" file?
The former.
> If you're seeing this behavior when using `raco s
Do the broken references show up when rendering docs with `raco setup`
or `raco pkg {install,update}`, or do they show up when running
`scribble` directly on the ".scrbl" file?
If it's the latter, then that makes sense. When you refer to a module
through a filesystem path, Scribble doesn't try to
I’ve always found that it’s more reliable to use fully-qualified package
names with `for-label`, e.g.
(require (for-label jordan/package))
rather than
(require (for-label "main.rkt"))
Once upon a time I had similar problems, and noticed that fully-qualified
names is the habit used in many inter
Hi all,
I have a file main.scrbl in the same directory as a file main.rkt. In the
.scrbl file, I have
(require (for-label "main.rkt"))
and several defproc and defstruct* forms. For some reason, one of my defstruct*
forms works as expected, while all of the other defstruct* and defproc forms
p
4 matches
Mail list logo
