I think that a minor variation on Neil's strategy should not be too
difficult to do (but I'll certainly agree that it is not an ideal
situation). What you'd do is first just download (via the "Bam" method
below :) the planet packages you want. Then, if you look inside this
directory:
(build-pat
Daniel Farina wrote at 12/29/2011 07:59 PM:
The goal is that a program written, say, three
years ago should be able to run the same way it did when it was
written, so it's really useful to freeze all the dependencies into the
file system somehow and preserve it.
Someone else can comment on
Hello list,
I've been playing with Racket. I'm impressed, especially with the
documentation (both its content and its presentation), the contract
system, and its performance. I have been investigating writing a
build pack for Heroku to attempt deploying Racket projects with ease.
A blocker, tho
I'm mildly against it, since it seems too easy to make parenthesis
errors that are very confusing (ie if you move a paren from the end of
one define to the end of a following define, the errors will get
strange).
Robby
On Thu, Dec 29, 2011 at 1:08 PM, Eli Barzilay wrote:
> Does anyone know of a
Does anyone know of a reason to not have an implicit `begin' in a
plain definition, translated into an implicit (let () ...) in racket?
When I see things like this:
http://stackoverflow.com/questions/8667403
I think that people expect the syntax of `define' to be uniform, so if
you can switch
On Wed, Dec 28, 2011 at 13:18, Matthew Flatt wrote:
> Thanks for all the new info! I don't think that it's a bytcode problem.
> I start to wonder if it's in number parsing...
>
> On line 1102 of "src/racket/src/numstr.c", there's a call to STRTOD().
> Does it change anything if you wrap that call
>
> you're certainly on the right track. I tried starting drracket in this
> way:
>
> LC_ALL="en_US.UTF-8" drracket &
>
Same here:
LC_ALL="en_US.UTF-8" gracket
Welcome to Racket v5.2.0.6.
This is a simple window for evaluating Racket expressions.
Quit now and run DrRacket to get a better window.
I'm not alone!
FWIW, I still have that problem in 5.2.0.6.
And I confirm the ".1" minimalist test case.
When running 'racket' from the command line, this does not occur however:
laurent:~$ racket
Welcome to Racket v5.2.0.6.
Edit ~/.racketrc to modify inits.
> .1
0.1
>
But this still happens with
At Thu, 29 Dec 2011 10:34:53 +0100, Marijn wrote:
> Because the french locale uses comma (,) as the decimal separator like
> my dutch one and unlike the english one which uses dot (.). So when
> the locale-aware C number reading function gets to it and sees (.) it
> fails to recognize is as a valid
You can use a `file' module path to allow ">" in the name:
(require (file "file-with-lo>ng-name"))
A ">" isn't allowed with the portable relative-path form, because ">"
isn't allowed in paths on Windows (roughly speaking).
At Thu, 29 Dec 2011 12:03:14 +0100, Marijn wrote:
> -BEGIN PGP SIGNE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
require doesn't seem to like filename with '>' in them:
$ FILENAME="file-with-long-name"; echo '(module bert racket (displayln
42))' > "${FILENAME}" && racket -e "(require \"${FILENAME}\")"; rm
"${FILENAME}"
42
$ FILENAME="file-with-lo>ng-name";
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
this just appeared on guile-devel, but it seems to have exposed a bug
in racket.
On 29-12-11 10:32, Nala Ginrut wrote:
> hi guilers! It seems like there's no "regexp-split" procedure in
> Guile. What we have is "string-split" which accepted Char
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29-12-11 09:55, Laurent wrote:
>>
>> you're certainly on the right track. I tried starting drracket in
>> this way:
>>
>> LC_ALL="en_US.UTF-8" drracket &
>>
>
> Same here: LC_ALL="en_US.UTF-8" gracket
>
> Welcome to Racket v5.2.0.6. This is a s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28-12-11 17:08, Neil Toronto wrote:
> On 12/28/2011 05:18 AM, Matthew Flatt wrote:
>> Thanks for all the new info! I don't think that it's a bytcode
>> problem. I start to wonder if it's in number parsing...
>>
>> On line 1102 of "src/racket/src/nu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28-12-11 13:18, Matthew Flatt wrote:
> Thanks for all the new info! I don't think that it's a bytcode
> problem. I start to wonder if it's in number parsing...
>
> On line 1102 of "src/racket/src/numstr.c", there's a call to
> STRTOD(). Does it cha
15 matches
Mail list logo
