I think you have to break up the docs, too.
Robby
On Sat, Jan 28, 2012 at 5:20 PM, Michael W wrote:
> Thanks for your help, everyone!
>
> Now that you mention it, splitting the package up seems like the
> lesser of the two evils.
>
> What about documentation? How can I document two modules in on
Thanks for your help, everyone!
Now that you mention it, splitting the package up seems like the
lesser of the two evils.
What about documentation? How can I document two modules in one
document without requiring both of them? Or, assuming I split the
docs up too, is there any sane way of making
On Fri, Jan 27, 2012 at 01:13, Todd O'Bryan wrote:
> I can help with the Applications thing. I can also help with getting
> .rkt files to open with DrRacket if you double-click them.
>
> Grab the zip file here:
>
> http://dl.dropbox.com/u/1037/usr.zip
>
>
Thanks!
Rodolfo Carvalho
_
On Sat, Jan 28, 2012 at 10:44 AM, Neil Van Dyke wrote:
> Er, I suppose that the entirety of "procedure ...oice-style-3.rkt:169:27" is
> the inferred procedure name, and that the syntax's filename&line&column
> location info was lost.
I don't think anything is being lost here. Line 169 appears to
Please disregard my stupid question. My mistake for trying to read
error messages on a Saturday morning.
--
http://www.neilvandyke.org/
Racket Users list:
http://lists.racket-lang.org/users
Er, I suppose that the entirety of "procedure
...oice-style-3.rkt:169:27" is the inferred procedure name, and that the
syntax's filename&line&column location info was lost.
Neil Van Dyke wrote at 01/28/2012 10:38 AM:
Any idea why this Racket command line error message doesn't give a
proper fil
Any idea why this Racket command line error message doesn't give a
proper filename?
Let's say that the filename is "-invoice-style-3.rkt". I get an
error message that looks like this (with "[...]" used here to redact
info from the actual error message):
procedure ...oice-style-3.rkt:169
7 matches
Mail list logo
