This one got me stumped for a while. I don't remember a case like
this ever occurring in the past, so I'm thinking that maybe this is a
regression?
In DrRacket, with debugging and stacktrace enabled in all the buffers
involved, when I run the file strano.rkt, I get this error:
Welcome to DrRacke
The line
(date-day quando)99
looks pretty suspicious; with the 99 there, the first branch of the
enclosing 'if' expression returns 8 values but the second branch returns
7 values.
Ryan
On 02/22/2013 09:48 AM, Pierpaolo Bernardi wrote:
This one got me stumped for a while. I don't rememb
On Fri, Feb 22, 2013 at 4:40 PM, Ryan Culpepper wrote:
> The line
>
> (date-day quando)99
>
> looks pretty suspicious; with the 99 there, the first branch of the
> enclosing 'if' expression returns 8 values but the second branch returns 7
> values.
Yes, that was the source of the error (a mista
On Fri, Feb 22, 2013 at 4:40 PM, wrote:
>
> + The list of colors is obtained by drawing the image on a white
> + background and then reading off the colors of the pixels that were drawn.
Is there a particular reason to choose white, as opposed to clear, for
the background in this test? Does d
No, I don't think it does. The drawing operation is called "over" and it
takes two colors (rgb, say), and an alpha and produces a color (rgb). So
you always start with some solid color in the background and draw the shape
on top of it, resulting in another color that some other shape can be drawn
o
I think that the lack of information about tail calls can be particularly
pernicious in the presence of multiple value errors. It would be good to do
better, but I'm not sure how. The errortrace library contains what we
currently do so you'd want to experiment there if you have an idea.
Robby
On
Ok, that makes sense.
I think you should maybe add the word "floor" in the nitty-gritty
documentation. You might also link from that discussion in the docs
to the Cairo docs here: http://cairographics.org/operators/ .
However, I can't find anything where they say they round down rather
than to ne
So, it has always behaved like this? I'm really surprised that I have
never been bitten by this before. 8^)
On Fri, Feb 22, 2013 at 10:51 PM, Robby Findler
wrote:
> I think that the lack of information about tail calls can be particularly
> pernicious in the presence of multiple value errors.
Well, I didn't try to explain _that_ part of the issue here (what I called
"b" in my message on the audit trail). It is much more complex and based
more on conjecture, so I'm hesitant to even try especially when the
existing discussion covers a more general, related problem that is likely
to satisf
I didn't investigate your program to be sure it isn't some other bug, but
the potential for this kind of bad behavior has always been with us, yes.
Robby
On Fri, Feb 22, 2013 at 3:59 PM, Pierpaolo Bernardi wrote:
> So, it has always behaved like this? I'm really surprised that I have
> never b
This is a pull request to make racket/scribble make-base-eval more like
racket/sandbox make-evaluator, which was useful to me, but I wasn't sure
if the current design avoided this for some reason.
This should be a backwards compatible change, but I have not tested it.
https://github.com/plt
On 2/22/13 7:05 PM, David Van Horn wrote:
This is a pull request to make racket/scribble make-base-eval more like
racket/sandbox make-evaluator, which was useful to me, but I wasn't sure
if the current design avoided this for some reason.
This should be a backwards compatible change, but I have
On Wednesday, Harry Spier wrote:
> Dear list members,
> I've just received an email that the bug report
>http://bugs.racket-lang.org/query/?cmd=view&pr=12375
> I initially submitted about this has been closed. But I'm not clear
> from the e-mail whether it is now intended to leave the commente
13 matches
Mail list logo
