On Thu, Sep 02 2010, Robby Findler wrote:
> I think you probably want to use the errortrace library. That's what
> DrRacket uses (and how it gets the better error messages).
That's exactly what i was looking for. Thanks a lot, Robby.
jao
_
For l
application/octet-stream
_
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/users
We're trying to configure our browsers to appropriately handle downloading
of .rkt files.
Should ".rkt" file types be designated as "application/racket" or
"application/drracket" or something else?
Some files could be treated as text, but in general this isn't true, once
images are inserted.
Tha
I think you probably want to use the errortrace library. That's what
DrRacket uses (and how it gets the better error messages).
Robby
On Sun, Aug 29, 2010 at 6:04 PM, Jose A. Ortega Ruiz wrote:
>
> In Racket 5.0.1, with, say, f.rkt containing:
>
> #lang racket
> (provide bar)
> (define (fo
Yes, this is a a rough one. You know the error is out there ... somewhere ...
Another one is exception traces not printing with a writer output
stream is closed error. Reports correctly in DrRacket, its at the
command line the problem is visible. I'll create a reproducible case
later this eveni
At Wed, 1 Sep 2010 19:58:40 -0400, "David T. Pierson" wrote:
> This concerned me because the src/README contains a warning about
> pthreads:
>
> > Unfortunately, Racket's normal stack handling and use of signals (for
> > its own thread scheduling) do not interact well with pthreads. Thus,
> > whe
Hello all,
I am compiling racket 5.0.1 for a Debian GNU/Linux system on an x86_64
machine.
I ran configure with no arguments, but noticed during the subsequent
make that files were being compiled with -pthread.
This concerned me because the src/README contains a warning about
pthreads:
> Unfort
> Back then they also discussed other representations of inexact numbers
> than floating point.
> Were there ever released a Scheme with, say, interval representation?
I'm pretty sure I've seen one, though it probably was one of the minor
implementations.
Shriram
_
2010/9/1 Carl Eastlund :
> If I have read the message correctly, Guy was quoting those three
> lines as well; they were written by Alan Bawden.
Oops. You are right. Guy used spaces to quote Alan, so I misread
what was quoted.
--
Jens Axel Søgaard
_
On Wed, Sep 1, 2010 at 4:00 PM, Jens Axel Søgaard wrote:
>
> Apropos philosophy. The rrrs mailing list is available online and
> contains various
> exchanges on inexact numbers. Here is one from Guy Steele with the
> memorable quote:
>
> INEXACT NUMBERS ARE NOT NUMBERS
>
>
2010/9/1 Stephen Bloch :
> I've been having an interesting discussion off-list with David Kay, but have
> concluded
> that we need the expertise of somebody more knowledgeable about Scheme/Racket
> and its philosophy.
Apropos philosophy. The rrrs mailing list is available online and
contains var
On Wed, Sep 1, 2010 at 7:30 AM, Prabhakar Ragde wrote:
>
> "Inexact" in Racket is code for IEEE double-precision floating point.
And for a particular, somewhat idiosyncratic `contagion' policy.
As Noel pointed out, the reason that we have floating-point is for speed.
(Well, also to approximate r
On Wed, Sep 01, 2010 at 12:15:27PM -0700, Joe Marshall wrote:
> On Wed, Sep 1, 2010 at 6:40 AM, Stephen Bloch wrote:
> > On Sep 1, 2010, at 9:29 AM, Matthias Felleisen wrote:
> >
> >> The #i indicates inexactness as far as computer arithmetic is concerned,
> >> that is, what the so-called 'machin
On Wed, Sep 1, 2010 at 6:40 AM, Stephen Bloch wrote:
> On Sep 1, 2010, at 9:29 AM, Matthias Felleisen wrote:
>
>> The #i indicates inexactness as far as computer arithmetic is concerned,
>> that is, what the so-called 'machine' level arithmetic supplies.
>
> And yet Scheme/Racket allows for inexa
Oh, right. That was a pretty big oversight, wasn't it! I've pushed
docs for that library.
Thanks,
Robby
On Wed, Sep 1, 2010 at 8:30 AM, Laurent wrote:
> Wow, that is even better than that!
> Digging a bit further, it uses the framework/splash module,
> which does everything I wanted (and more),
zo-parse is a work in progress. We're discovering as we go what the
contracts should be. This is a case where the documentation must be
wrong. We'll change it.
Jay
On Wed, Sep 1, 2010 at 11:22 AM, Danny Yoo wrote:
> I'm using Racket 5.0.1 and the compiler/zo-parse module. On some of
> the struc
I'm using Racket 5.0.1 and the compiler/zo-parse module. On some of
the structures I'm getting back, I'm seeing that a case-lam structure
has a clause that's an indirect, rather than a lam. The documentation
for 5.0.1 says that a clause has to be a lam though. Is this
intentional?
__
Stephen Bloch writes:
An example in my textbook is
(define TANK-CAPACITY-GALLONS #i13.6) (define MPG #i28)
because the capacity of a gas tank, and miles-per-gallon fuel
efficiency, are based on physical measurements and therefore
inherently inexact.
I think this is misguided. The proper resp
On Sep 1, 2010, at 7:40 AM, Stephen Bloch wrote:
> On Sep 1, 2010, at 9:29 AM, Matthias Felleisen wrote:
>
>> The #i indicates inexactness as far as computer arithmetic is concerned,
>> that is, what the so-called 'machine' level arithmetic supplies.
>
> And yet Scheme/Racket allows for inexac
On Sep 1, 2010, at 9:29 AM, Matthias Felleisen wrote:
> The #i indicates inexactness as far as computer arithmetic is concerned, that
> is, what the so-called 'machine' level arithmetic supplies.
And yet Scheme/Racket allows for inexact integers, whereas no computer I know
of has an inexact int
Wow, that is even better than that!
Digging a bit further, it uses the framework/splash module,
which does everything I wanted (and more), even with the gauge
that progresses automatically, and it works like a charm out of the box!
Awesome.
And it is so simple to use:
<<<
#lang racket/base
(requ
On Sep 1, 2010, at 9:14 AM, Stephen Bloch wrote:
> (since the only arithmetic involved is addition, subtraction, multiplication,
> and division), so the argument could be made that putting #i in there is
> distracting and pedantic.
I second this opinion (re pedantic).
;; ---
The #i indicat
On Wed, Sep 1, 2010 at 2:14 PM, Stephen Bloch wrote:
irrational. Likewise,
>
> The question is under what circumstances (if any) you would want to mark
> something as inexact that DIDN'T come from an irrational-valued library
> function or constant.
>
Speed, speed, speed, and more speed. Some
On Sep 1, 2010, at 9:14 AM, I wrote:
> The "#i" indicates that a number is inexact, and that further computation
> based on it should be interpreted accordingly. The Scheme/Racket numeric
> libraries automatically mark as "inexact" most results of trig, exponential,
> log, sqrt, and similar fu
I've been having an interesting discussion off-list with David Kay, but have
concluded that we need the expertise of somebody more knowledgeable about
Scheme/Racket and its philosophy.
The "#i" indicates that a number is inexact, and that further computation based
on it should be interpreted ac
Thanks again! Very helpful.
On Wed, Sep 1, 2010 at 14:16, Robby Findler wrote:
> collects/drracket/drracket.rkt does something similar to set up
> compilation handlers and (optionally) a profiler that I use for
> performance debugging, and then it loads
> drracket/private/drracket-normal.rkt whic
collects/drracket/drracket.rkt does something similar to set up
compilation handlers and (optionally) a profiler that I use for
performance debugging, and then it loads
drracket/private/drracket-normal.rkt which does the splash screen bit.
Robby
On Wed, Sep 1, 2010 at 7:11 AM, Laurent wrote:
> E
Excellent! Thanks a lot!
By any chance, do you remember the name of the file that does that?
(Don't take more than 10s for this question, it's not worth it.)
On Wed, Sep 1, 2010 at 14:00, Robby Findler wrote:
> A minimal amount of stuff is loaded (roughly what is loaded when
> gracket itself star
A minimal amount of stuff is loaded (roughly what is loaded when
gracket itself starts up) and then the splash screen is opened and the
rest of drracket is loaded via a dynamic-require. Also, progress on
the splash screen's gauge% is made each time a file is loaded, which
is monitored by the load-h
Noel Welsh wrote at 08/31/2010 04:36 PM:
In general this is a huge problem (equivalent, I think, to the "sufficiently smart
compiler" problem, which itself is equivalent to solving AI).
What Noel said. Though, it might be a useful thing for the Racket
interpreter (compiler) to have hooks
30 matches
Mail list logo
