Re: [racket-dev] Release Announcement for v5.0.1 -- final version

2010-08-03 Thread Michael Sperber

Matthias Felleisen matth...@ccs.neu.edu writes:

 works in Beginner. It turns out however that even the German docs are
 broken. I should have explored more when Mike merged this in. Then
 again, I doubt we will have many Americans reading these docs.

What's broken?

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] LLVM

2010-08-03 Thread Eli Barzilay
On Aug  3, Paul Steckler wrote:
 On Tue, Aug 3, 2010 at 10:41 AM, Matthias Felleisen
 matth...@ccs.neu.edu wrote:
  Eli and an undergraduate (Alex Friedman) started on this a few
  years ago and got reasonably far. They could compile a bunch of
  small stuff, and the LLVM developer was highly responsive to
  requests back then (still at UIUC).

It wasn't actually compiling code, it was more a scheme-like assembly
language which got far enough to run useful bits of code.  We also had
a lightning interface before the LLVM thing.


  But Matthew's effort on jitting via gnu lightning was better and
  so the llvm project was abandoned.

Matthew actually wrote a jitter for bytecode, and lightning turned out
fine for that.  LLVM has a nice interface and lots of optimizations
(some tied to how it represents assembly code) -- but the system
itself is pretty big, which made it much less appealing as a target
for jitting.  (It's roughly like swallowing GCC into Racket.)


 Interesting; I wasn't aware of GNU lightning.
 
 Does that mean that mzc currently targets lightning, or is that just
 used in the JIT?

Both of these are unrelated to mzc -- and the current use of lightning
is only for jitting.  If you're talking about using the LLVM C
compiler, then that's a different issue (and I think that some people
have tried that, but I don't remember who or whether it was
successful).

-- 
  ((lambda (x) (x x)) (lambda (x) (x x)))  Eli Barzilay:
http://barzilay.org/   Maze is Life!
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Release Announcement for v5.0.1 -- final version

2010-08-03 Thread Matthias Felleisen

On Aug 3, 2010, at 3:08 AM, Michael Sperber wrote:

 
 Matthias Felleisen matth...@ccs.neu.edu writes:
 
 works in Beginner. It turns out however that even the German docs are
 broken. I should have explored more when Mike merged this in. Then
 again, I doubt we will have many Americans reading these docs.
 
 What's broken?

I found two things so far: 

1. the basic signatures are lowercase in the docs, but are uppercase for real. 

2. When you restrict a function with a signature, you can still misapply it in 
the REPL: 


(: f (Integer - Integer))
(define (f x) x)
(f hello) ;; in Defs: violation of signature 

;; in REPL: returns hello

The biggest flaw is mine. The code is in the base but there's no documentation. 

-- Matthias



_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


[racket-dev] x86_64 libs not available to 32-bit ffi, right?

2010-08-03 Thread John Clements
Reality check: I can't use the Racket ffi libraries to load 64-bit x86_64 
shared libs, can I?

John



smime.p7s
Description: S/MIME cryptographic signature
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev

Re: [racket-dev] Tech links with custom text

2010-08-03 Thread Vincent St-Amour
That was fast! Thanks!

Vincent


At Tue, 3 Aug 2010 12:49:03 -0600,
Matthew Flatt wrote:
 
 At Tue, 03 Aug 2010 14:34:40 -0400, Vincent St-Amour wrote:
  While writing documentation, I came across cases where I would have
  wanted to link to technical terms (using the tech function) without
  having the technical term itself be the text of the link.
  
  For example, I wanted to link to the definition of inexact number,
  but I wanted the text of the link to be inexact instead of inexact
  number.
  
  Is there a way to do that?
 
 The `tech' and `techlink' functions now accept an optional `#:key'
 argument to specify the key separate from the rendered content.
 
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev