I think you hit on the distinction when you use the terms "procedure" and
"procedure application". It is correct to say that a procedure returns a
value and that an application of that procedure has a value. (since Scheme
has first-class procedures, it's also true that a procedure has a value,
but
That's a good point, Tobias.
I'd actually be fine with `define-logger' acting like
`define/provide-logger' -- just go ahead and provide them all.
Because I don't see opacity being such a useful option for a logger,
as opposed to something like a struct?
On Fri, Sep 7, 2012 at 12:21 PM, Tobias Ha
Thanks for these great new features!
A (logger-out name) form for provide, exports all functions generated by
define-logger might be useful too.
Tobias
On Fri, 07 Sep 2012 16:28:13 +0200, Matthew Flatt
wrote:
Based on the discussion, plus some extra off-list discussion with Greg,
I've m
I meant to post this earlier. I've really enjoyed your blog. The
series on continuations was particularly helpful for me.
Two areas I've found very challenging to grasp are continuations and
macros. I think multiple reasons why, but one is that I simply need to
slow down, take it step by step, wor
I notice Octopress' {% codeblock %} uses pygments to do highlighting,
as do GitHub and Bitbucket. As/when each of these pulls a newer
pygments, they should pick up the new RacketLexer that pygments merged
a few weeks ago.
At which point:
{% lolspeak %}
Iz in ur filez, makin ur codez haz rainbowz.
Based on the discussion, plus some extra off-list discussion with Greg,
I've made the following changes:
* The `log-error', etc. forms still treat a single subexpression as a
literal string for the log message, but now they treat multiple
subexpressions as arguments to `format'.
This ch
6 matches
Mail list logo
