3 ms·
> Racket eliminates the hard boundary between library and language, overcoming a seemingly intractable conflict I don't buy it. A language extension means th
by MaxBarraclough 9y ago
> Racket eliminates the hard boundary between library and language, overcoming a seemingly intractable conflict
I don't buy it.
A language extension means the syntax wouldn't ever be valid in the base language. The fact that Racket defines its 'for' construct using macros/functions/whatever is cute, but I see no reason to pretend it's a language extension.
- soegaard 9y ago> A language extension means the syntax wouldn't ever be > valid in the base language. Well, this works: #lang base-without-for (require the-for-library) ...use for here... Of course if the author of `for` has made a `base-with-for` language, then I can just use: #lang base-with-for ...use for here...
- shakna 9y ago> I don't buy it. > A language extension means the syntax wouldn't ever be valid in the base language. Sure. (struct pt ([x : Real] [y : Real])) That's not valid Racket, but is valid Typed Racket. A more extreme example: int main(int argc, char** argv) { return 0; } That's C! Oh wait, it's the C #lang [0]... Which means you can things like: base.rkt: #lang C float f( float x1, float x2 ) { return x1 / x2; } main.rkt: #lang racket (require base) f(10.2, 1.8) Those syntaxes aren't compatible, by any stretch. The magic is, Racket gives you access to powerful pre-processing, in the form of some amazing reader macros. What syntax you use, doesn't really matter, so long as you provide that bridge. They're incompatible syntax, with a custom made parser allowing data to flow both ways. [0] https://github.com/jeapostrophe/c https://github.com/jeapostrophe/c
- mcguire 9y agoShouldn't that second example be (f 10.2 1.8)
- shakna 9y agoYep. My bad.
- username223 9y agoWhere does the conversion between C's simple "float" and Scheme's notion of numbers take place? Does the call from "#lang racket" check and convert the arguments before passing to a simple f(), or does a complex f() check and convert its parameters?
- shakna 9y agoIt depends on the implementation, that's for the expander to handle. In the case of the implementation I listed, it passes it on literally, and compiles it and runs it, and then takes the output and passes it back to Racket. [0] [0] https://github.com/jeapostrophe/c/blob/master/c/lang/runtime.rkt https://github.com/jeapostrophe/c/blob/master/c/lang/runtime...
- username223 9y agoIt shells out to the C compiler (hard-coded as "cc") for every function? Oof. That's a pretty limited FFI. Or maybe I wasn't clear. If Scheme tries to pass a double/bignum/whatever to the C function that expects the float, where is the error caught?
- shakna 9y agoIt's not Scheme that does the passing, just to be clear, it's the library. In this case, it's just throwing strings around without changing anything. No passing to transform a bignum, no bounds checking. Just tries to run it. (Racket does have a decent FFI [0], but this library is just for classroom example stuff. Not serious work.) [0] https://docs.racket-lang.org/foreign/index.html https://docs.racket-lang.org/foreign/index.html
- gus_massa 9y agoThe base language is not "racket". The base language is "#%kernel". The langue "racket" is implemented in "racket/base" that is implemented in "pre-base" that is implemented in #%kernel. If you want to use `for` you must use "racket" or "racket/base" or "pre-base", because it isn't defined in #%kernel. If you want to use `match` you must use "racket" because it isn't defined in the other three languages. The language "#%kernel" has a minimal syntaxes defined, so it's painful to use.