define-runtime-path mainly does two things.
The first, which you allude to, is that it exposes to the compiler
than you need this path and so it should include the file if you were
to create an executable and arrange things so that accessing it via
the runtime path gives you the embedded file. I don't think you need
this feature.
The second, is that you can embed paths relative to the source file
into the code rather than having paths be relative to the current
working directory when you run it. So, if I run your original program
from /home/jay but it lives in /home/jay/class/cs99/code then
lessons-dir is /home/jay/class/cs99/lessons and not /home/lessons.
Jay
> --
> You received this message because you are subscribed to the Google Groups
> "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
racket-dev+...@googlegroups.com.
> To post to this group, send email to
racke...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/racket-dev/7f9ffb92-0662-4df8-ab04-8535d93a5e25%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.
--
-=[ Jay McCarthy
http://jeapostrophe.github.io ]=-
-=[ Associate Professor PLT @ CS @ UMass Lowell ]=-
-=[ Moses 1:33: And worlds without number have I created; ]=-