It is extremely unlikely that out of date .zo files could cause this, altho
it is, in theory, possible.
Robby
On Wed, Oct 23, 2013 at 7:55 PM, Erik Pearson wrote:
> Thanks Robby, a nice teaching gift.
>
> I think the problem has "gone away". Realizing my ad-hoc test was run from
> the file in
Thanks Robby, a nice teaching gift.
I think the problem has "gone away". Realizing my ad-hoc test was run from
the file in which url triggers the error, I set about to embed the test in
the file / dr racket window that generates url.
I ran a test function, starting very simple and step by step ge
Since there's little background here, I thought I'd just add that this
feature you're coming across is one of the critical things that underpins
Racket and differentiates it from languages like python and ruby. That is,
what you're seeing is that Racket has a way to make unforgeable values.
This ab
Correct
On Wed, Oct 23, 2013 at 4:38 PM, Erik Pearson wrote:
> On Wed, Oct 23, 2013 at 3:31 PM, Jay McCarthy
> wrote:
>>
>> Here are two ideas.
>>
>> 1) You simply have an old use of the original net/url. When # is
>> printed, it uses the symbolic name and you can't really figure out
>> what the
Or you defined
(struct url ...)
somewhere :-)
On Oct 23, 2013, at 6:31 PM, Jay McCarthy wrote:
> Here are two ideas.
>
> 1) You simply have an old use of the original net/url. When # is
> printed, it uses the symbolic name and you can't really figure out
> what the underlying code came f
On Wed, Oct 23, 2013 at 3:31 PM, Jay McCarthy wrote:
> Here are two ideas.
>
> 1) You simply have an old use of the original net/url. When # is
> printed, it uses the symbolic name and you can't really figure out
> what the underlying code came from. I would do a grep to make sure
> this is not th
Here are two ideas.
1) You simply have an old use of the original net/url. When # is
printed, it uses the symbolic name and you can't really figure out
what the underlying code came from. I would do a grep to make sure
this is not the case.
2) You are using namespaces somewhere and actually have
On Oct 23, 2013, at 6:25 PM, Erik Pearson wrote:
> Excuse my poor experience with contracts, this is probably an easy one.
>
> I'm using a copy of net/url and have a strange problem. The copied library is
> working fine in general, but this problem cropped up today:
>
> struct:exn:fail:con
Excuse my poor experience with contracts, this is probably an easy one.
I'm using a copy of net/url and have a strange problem. The copied library
is working fine in general, but this problem cropped up today:
struct:exn:fail:contract:blame url-port: contract violation
expected: url?
given: #
in:
9 matches
Mail list logo
