On Thu, Jun 16, 2011 at 5:44 AM, Eli Barzilay <e...@barzilay.org> wrote: >> If, for some reason, the best we can do is improve the error >> message, how about reporting it in terms of the Scribble forms we're >> actually using: >> >> "examples: cannot read output of given evaluator, expected a string >> but got: #f" > > That would involve changing more than I'm comfortable with in that > file. For example, > > - `interaction' is a macro that expands to `interaction0', > > - which is a macro that expands to `titled-interaction', > > - which is a macro that expands to `do-titled-interaction', > > - which is a function that > - calls `do-eval' to do the evaluation and get the resulting > values and outputs > - and then calls the `interleave' function > - which calls `format-output' to show the two outputs. > (which is where I put the check) > > So 'interaction should be threaded through all of that to get that > error message, and checking whether any of these are also part of the > known interface and in that case have internal versions with the > additional argument.
This is not a good argument, if I'm understanding you correctly. I think you're saying "it is too annoying to give a good error message" which is not a reasonable argument. Robby _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
