On Aug 6, 2014, at 4:33 PM, Jens Axel Søgaard wrote:
> 2014-08-06 16:10 GMT+02:00 Robby Findler :
>> I think this is awesome too!
>>
>> Is there some way we can use this to help make Racket better, do you think?
>
> That wasn't the motivation per se, but it might have some potential uses.
> A
> Whalesong do not interpret the bytecodes directly, so I didn't
> look for hints there.
(Note: there was a preliminary simulator used for test cases in
2bc4b2a224fe7a485a1060c69ebde925cecdeb05)
Racket Users list:
http://lists.racket-lang.org/users
2014-08-06 16:10 GMT+02:00 Robby Findler :
> I think this is awesome too!
>
> Is there some way we can use this to help make Racket better, do you think?
That wasn't the motivation per se, but it might have some potential uses.
A simple application would be to collect statistics of the bytecodes u
2014-08-06 16:07 GMT+02:00 Jay McCarthy :
> This is awesome, Jens.
>
> I'd like to have more Racket VMs for experiments like JavaScript and
> LLVM (to get on to iOS better?). I wonder if you were able to use the
> Whalesong bytecode interpreter during the coding of this?
Whalesong do not interpret
I think this is awesome too!
Is there some way we can use this to help make Racket better, do you think?
Would it be useful as a test oracle? Is there a way to maybe
re-interpret the function definitions (say put them into a different
"#lang") you've written to get some kind of a cool random byte
This is awesome, Jens.
I'd like to have more Racket VMs for experiments like JavaScript and
LLVM (to get on to iOS better?). I wonder if you were able to use the
Whalesong bytecode interpreter during the coding of this?
Jay
On Mon, Aug 4, 2014 at 4:23 PM, Jens Axel Søgaard wrote:
> Hi All,
>
>
Hi All,
To see how Racket's bytecodes work I have implemented an evaluator in Racket.
The best feature is the extensive amount of comments.
https://github.com/soegaard/meta/blob/master/runtime/racket-eval.rkt
Comments and patches are welcome,
Jens Axel Søgaard
Racket User
7 matches
Mail list logo
