Sorry for the delay in getting back to you.
I think that what you're seeing here is just the imprecision in stack
traces that has to do with how Racket's optimizer works and how the
low-level stack (here by "low-level" I mean the approximate ones that are
coming from a low-level of the implementat
Is there a pedagogic reason why the Systems Programming guide
explicitly discourages running through DrRacket?
There's a leading paragraph in the intro:
To get into the spirit of this tutorial, we suggest that you set
DrRacket aside for a moment, and switch to raw racket in a terminal.
But f
It emphasizes that Racket is broadly applicable, and works both in an
IDE environment, and in a text editor/shell environment, each of which
is preferred by large groups of developers.
Sam
On Thu, Jan 31, 2013 at 2:38 PM, Danny Yoo wrote:
> Is there a pedagogic reason why the Systems Programming
On Thu, Jan 31, 2013 at 4:01 PM, Sam Tobin-Hochstadt wrote:
> It emphasizes that Racket is broadly applicable, and works both in an
> IDE environment, and in a text editor/shell environment, each of which
> is preferred by large groups of developers.
Ok, this idea is important. I'm just not sure
Also, no matter what you do, there are a certain kind of hackers that
will never dump their console for all the gui in the world. (And the
size of this crown is not negligible.)
Four hours ago, Sam Tobin-Hochstadt wrote:
> It emphasizes that Racket is broadly applicable, and works both in
> an I
On Thu, Jan 31, 2013 at 8:23 PM, Eli Barzilay wrote:
> Also, no matter what you do, there are a certain kind of hackers that
> will never dump their console for all the gui in the world. (And the
> size of this crown is not negligible.)
Ok. I think Matthew's note is good enough then.
_
6 matches
Mail list logo
