An hour and a half ago, Carl Eastlund wrote:
> I get the following error every time I try to connect:
>
> ssh_exchange_identification: Connection closed by remote host
> fatal: The remote end hung up unexpectedly
If you had problems logging in a few times the server will blacklist
your IP, which
I get the following error every time I try to connect:
ssh_exchange_identification: Connection closed by remote host
fatal: The remote end hung up unexpectedly
Carl Eastlund
_
For list-related administrative tasks:
http://lists.racket-lang.org/l
There is one thing defined at phase 0, module-begin. The module exports
a bunch of stuff
(provide (rename-out [module-begin #%module-begin])
(except-out (all-from-out scheme/base) #%module-begin)
(all-from-out scheme/unit)
(all-from-out scheme/contract)
(for-syn
That makes sense. For now, I am fine with this very first-order approximation.
Thanks
On Nov 29, 2010, at 5:32 PM, Jon Rafkind wrote:
> There is one thing defined at phase 0, module-begin. The module exports
> a bunch of stuff
>
> (provide (rename-out [module-begin #%module-begin])
>
If I ignore the > 100% exports here, I get something like an average of 40%
exported identifiers. Thanks -- Matthias
On Nov 29, 2010, at 4:24 PM, Jon Rafkind wrote:
> On 11/29/2010 12:20 PM, Jon Rafkind wrote:
>> I hacked my old tool to get a first approximation and ran it on all the
>> files
Thanks, that's great. But what does this mean:
"collects/racket/signature/lang.rkt defined 1 exported 2747"
-- Matthias
On Nov 29, 2010, at 4:24 PM, Jon Rafkind wrote:
> On 11/29/2010 12:20 PM, Jon Rafkind wrote:
>> I hacked my old tool to get a first approximation and ran it on all the
>
On 11/29/2010 12:20 PM, Jon Rafkind wrote:
> I hacked my old tool to get a first approximation and ran it on all the
> files of the collects/racket tree. I can run it on the entire collects
> tree if you want, but its sort of slow so it will take a while. I
> couldn't expand all the files because l
I hacked my old tool to get a first approximation and ran it on all the
files of the collects/racket tree. I can run it on the entire collects
tree if you want, but its sort of slow so it will take a while. I
couldn't expand all the files because local requires failed, I'll try to
fix that.
collec
On Mon, Nov 29, 2010 at 9:36 AM, Jay McCarthy wrote:
> I really dislike such global imperative state, but it should be easy
> to write response/hooks or something to provide this as a library. The
> default response will be a streaming output though, so it will be easy
> to make everything efficie
This kind of thing has happened many times for other parts of the
system (the class system is a good example). We have generally tried
to avoid so much breakage and I think we should here. One technique is
to have a new name for the new version (or a new name for the old one
if that is more appropr
I really dislike such global imperative state, but it should be easy
to write response/hooks or something to provide this as a library. The
default response will be a streaming output though, so it will be easy
to make everything efficient in extensions.
Jay
On Mon, Nov 29, 2010 at 3:29 AM, Nevo
On Mon, Nov 29, 2010 at 3:41 AM, Nevo wrote:
> Hi Jay:
> I have a question as to what you refer as "backwards incompatible".
Most Web applications will become contract violators because they are
returning Xexprs directly to send/suspend, etc rather than returning
response data structures. I wil
Hah.. Okay, then I will fill the bug reports in time once this change is in.
Thank you!
On 29 November 2010 17:43, Noel Welsh wrote:
> Those libs will be supported in a more or less active manner depending
> on us receiving bug reports and our workload at the time.
>
> N.
>
> On Mon, Nov 29, 201
Those libs will be supported in a more or less active manner depending
on us receiving bug reports and our workload at the time.
N.
On Mon, Nov 29, 2010 at 8:41 AM, Nevo wrote:
> Hi Jay:
> I have a question as to what you refer as "backwards incompatible".
> Will the old way (bytes response
Hi Jay:
I have a question as to what you refer as "backwards incompatible".
Will the old way (bytes response format) be workable since currently my
blog server is setup by using some libs from "untyped" from planet and I'm
not sure if this change will have any impact to those libs? Thanks,
rega
On 28 November 2010 00:31, YC wrote:
>
>
> I agree with Neil that xexpr or sxml are very nice representations of html
> as well. Given their inherent advantage I think an extensible response
> mechanism might work better:
>
>1. create hooks to handle different response types
>2. let the d
16 matches
Mail list logo
