About a month ago, Matthias Felleisen wrote: > > On Jul 7, 2013, at 12:08 AM, Eli Barzilay <e...@barzilay.org> wrote: > > > It would be nice to have some way of doing it with contracts, but > > that's obviously impractical -- so I think that a good way to > > solve it and other such problems is to add a parameter for the > > name used in read errors, and making `raise-read-error' behave in > > a similar way to `raise-syntax-error' with the parameter used as > > the `foo:' part of the error message. > > Boy I like this. I can't remember how often I have code up something > like '#:function' and thought this is a general problem worthy of a > solution.
My point was that this is a problem with readers -- where you often wrap some reading function (that can fail) by your own reader function, and any reading problems should therefore be attributed to your reader. That's why I think that a parameter would be a nice way to address this. -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _________________________ Racket Developers list: http://lists.racket-lang.org/dev