The documentation of get-pure-port/headers seems to suggest that it
returns the same thing
(call/input-url u
(lambda (p)
(define hs (purify-port p))
(values p hs)))
would, except that it also handles redirections
However, it does not actually give the value returned by
purify-port---it
I have written code with get-pure-port/headers and I would very much like to
get the status line. Not an external opinion though.
On Aug 2, 2012, at 8:54 AM, Jay McCarthy wrote:
The documentation of get-pure-port/headers seems to suggest that it
returns the same thing
(call/input-url u
Below is the third draft of the release announcement items for
v5.3. Let me know if I've missed something.
* Submodules are nested module declarations that can be loaded and
run independently from the enclosing module. For an overview of
submodules, see
I think the below should be somewhat reordered, as follows:
On Thu, Aug 2, 2012 at 11:16 AM, Ryan Culpepper r...@cs.utah.edu wrote:
* Most error messages use a new multi-line format
* The new `racket/generic' library
* The contract library comes with support for
* The futures visualizer
*
On 08/02/2012 11:16 AM, Ryan Culpepper wrote:
[...]
* There is now a very complete completion code for zsh. It is not
included in the distribution though, get it at: http://goo.gl/DU8JK
(This script and the bash completions will be included in the
standard installers in future
At Thu, 02 Aug 2012 11:28:56 -0400,
Ryan Culpepper wrote:
On 08/02/2012 11:16 AM, Ryan Culpepper wrote:
[...]
* There is now a very complete completion code for zsh. It is not
included in the distribution though, get it at: http://goo.gl/DU8JK
(This script and the bash
+1
On Aug 2, 2012, at 11:33 AM, Vincent St-Amour wrote:
At Thu, 02 Aug 2012 11:28:56 -0400,
Ryan Culpepper wrote:
On 08/02/2012 11:16 AM, Ryan Culpepper wrote:
[...]
* There is now a very complete completion code for zsh. It is not
included in the distribution though, get it at:
Why? They are currently grouped according to features, e.g., class contracts
and class abstract, and placed into adjacent groups, e.g., classes next to
generics.
On Aug 2, 2012, at 11:24 AM, Sam Tobin-Hochstadt wrote:
I think the below should be somewhat reordered, as follows:
On Thu,
On Thu, Aug 2, 2012 at 11:44 AM, Matthias Felleisen
matth...@ccs.neu.edu wrote:
Why? They are currently grouped according to features, e.g., class contracts
and class abstract, and placed into adjacent groups, e.g., classes next to
generics.
I attempted to order them by (my impression of)
When you have a huge enumeration, like we do here, I think importance is
extremely difficult to evaluate for a reasonably large audience but topics are
easy to group. If you don't mind, let's leave it alone.
On Aug 2, 2012, at 11:46 AM, Sam Tobin-Hochstadt wrote:
On Thu, Aug 2, 2012 at
First, the grouping was not at all obvious from the text of the
release announcement. Second, we (meaning the release manager) should
make an effort to sort by importance. Release announcements are one
of the primary ways that we communicate the cool things we're doing to
our users. We should
[Aggregated reply.]
10 hours ago, Ryan Culpepper wrote:
* A new `json' library (derived from Dave Herman's PLaneT library) for
parsing and generating JSON comes with the distribution.
Please revert this to the original phrasing. The code is derived in
a weak sense, since pretty much all
12 matches
Mail list logo
