Hello folks,
Working on some code involving FFI calls to a Rust dylib, I found out that it
seems that returns values get eaten now.
Of course, almost the same code was working a week ago. In between, I optimised
my Rust code a lot and upgraded my MacOs to Sierra. Just today I returned to
work
On Oct 7, 2016, at 9:47 AM, Robby Findler wrote:
> For just running examples and looking at their output, a simpler way
> is probably to use codeblock-pict from the pict/code library. That
> requires you to set up your lexer as a module lexer, but doesn't have
> the disadvantage that you have to r
For testing your lexer, I think you probably want to write a helper
function that takes in a lexer and a port and returns a list of tokens
and then go from there. There is one such here (the lex function):
https://github.com/racket/syntax-color/blob/master/syntax-color-test/tests/syntax-color/modu
Suppose I want to test `my-lexer` as a DrRacket syntax colorer. My idea is to
create a miniature editor with `color-text%` and display it in DrRacket with
`editor-snip%`. The code below will display a basic editor with black text.
Q: How can I attach `my-lexer` to this editor so that the text i
4 matches
Mail list logo
