<div class="gmail_quote">On Mon, Jul 14, 2008 at 1:13 PM, Anton Tayanovskyy <<a href="mailto:anton.tayanovskyy@gmail.com">anton.tayanovskyy@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> From the manual: A sequence #lang 〈name〉 is equivalent to #reader 〈name〉/lang/reader <a href="http://docs.plt-scheme.org/reference/reader.html#%28part._parse-reader%29" target="_blank">http://docs.plt-scheme.org/reference/reader.html#(part._parse-reader)</a> So you can use #lang instead of #reader. </blockquote><div> Yes - except `#lang` cannot handle all module spec such as `lib` or `planet` module path.  `s-exp` will use the next datum as the module path, but AFAICT `s-exp` doesn't allow the use of custom reader (which my custom language requires), and hence I ended up having to use #reader and hack my own s-exp module if I want to use `(planet ...)` as the module resolver.  </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Not sure what your exact problem is, but I guess you can always hack the s-exp/lang/reader.ss module to suit your needs, making, for instance, a my-s-exp/lang/reader.ss module. </blockquote><div> That's what I did, thanks.  But in order to use `(planet ...)` path resolver - it appears I need to use `#reader` instead of `#lang`.  Hence I'm interesting in seeing `#lang` support more module specs.  Thanks, yc </div></div>