Re: [racket-dev] [racket] Profiling mostly macro-generated definitions?

2012-09-17 Thread Matthew Flatt
At Fri, 31 Aug 2012 07:35:12 -0600, Matthew Flatt wrote: Sorry that I've been slow to catch on in this thread... Yes, stack traces in JIT mode don't really work in Win64, and that's why `profile' gives no information. I'll try to improve Win64 context support sometime soon. I forgot to

Re: [racket-dev] What are single flonums good for?

2012-09-17 Thread Neil Toronto
On 09/16/2012 04:10 PM, Matthias Felleisen wrote: Suppose we had started Racket long ago and maintained it until now. Then we'd be looking at 8bit, 16, 32, and 64 precision. In some N years from now, we may need 128. (Actually there were machines in the past that did, but never mind.) Could

Re: [racket-dev] Racket Questions?

2012-09-17 Thread Neil Toronto
I'll implement `flmodulo' in the math library, which already has `flodd?' and `fleven?'. These things can be tricky to get right; for example, most people wouldn't notice that their implementation is wrong on negative inputs. I'll probably also do `flremainder'. Neil ⊥ On 09/15/2012 12:45

[racket-dev] Is this expected behavior?

2012-09-17 Thread Jordan Schatz
On a freshly pulled and compiled racket: jordan@serenity ~ racket Welcome to Racket v5.3.0.24. (enter! slideshow/pict) define-values: assignment disallowed; cannot re-define a constant constant: invoke-unit/core in module: /usr/local/lib/racket/collects/racket/unit.rkt context...:

Re: [racket-dev] What are single flonums good for?

2012-09-17 Thread Vincent St-Amour
At Sun, 16 Sep 2012 17:10:01 -0500, Matthias Felleisen wrote: Suppose we had started Racket long ago and maintained it until now. Then we'd be looking at 8bit, 16, 32, and 64 precision. In some N years from now, we may need 128. (Actually there were machines in the past that did, but never

Re: [racket-dev] syntax parsing: must be a nice pattern-y way to do this

2012-09-17 Thread John Clements
On Sep 16, 2012, at 5:48 PM, Ryan Culpepper wrote: See 'define-template-metafunction' in syntax/parse/experimental/template. Remember to change the relevant occurrences of 'syntax' to 'template'. Neat! I'm guessing, though, that I probably shouldn't release planet packages that depend on

Re: [racket-dev] Is this expected behavior?

2012-09-17 Thread Asumu Takikawa
On 2012-09-17 11:39:55 -0600, Jordan Schatz wrote: On a freshly pulled and compiled racket: This is a known bug, see PR 13096: http://bugs.racket-lang.org/query/?cmd=viewpr=13096 It does indeed seem to be an issue with submodules, but the precise problem is hard to track down. Cheers, Asumu

Re: [racket-dev] syntax parsing: must be a nice pattern-y way to do this

2012-09-17 Thread Ryan Culpepper
On 09/17/2012 02:20 PM, John Clements wrote: On Sep 16, 2012, at 5:48 PM, Ryan Culpepper wrote: See 'define-template-metafunction' in syntax/parse/experimental/template. Remember to change the relevant occurrences of 'syntax' to 'template'. Neat! I'm guessing, though, that I probably

Re: [racket-dev] syntax parsing: must be a nice pattern-y way to do this

2012-09-17 Thread John Clements
On Sep 17, 2012, at 11:27 AM, Ryan Culpepper wrote: On 09/17/2012 02:20 PM, John Clements wrote: On Sep 16, 2012, at 5:48 PM, Ryan Culpepper wrote: See 'define-template-metafunction' in syntax/parse/experimental/template. Remember to change the relevant occurrences of 'syntax' to

[racket-dev] Segmentation fault 11?

2012-09-17 Thread Danny Yoo
I'm seeing weirdness when trying to import Dave Herman's memoize package on Racket 5.3: ;;; (require (planet dherman/memoize:3:1)) WARNING: collected information for key multiple times: '(index-entry (mod-path (planet schematics/sake))); values: Segmentation fault: 11 ;;; I'm on

[racket-dev] Top level is hopeless or bug?

2012-09-17 Thread Asumu Takikawa
Hi all, Is the following interaction the expected behavior here or is it a bug? Welcome to Racket v5.3.0.24. - (module foo racket (define x 0) (provide x)) - (require 'foo) - x 0 - (module foo racket (module* bar #f (define x 1) (provide x))) - x ; readline-input:4:0: link: module mismatch; ;