42 ms·
For reference: In D, you could just take a HTML parser then run it at compile time without writing any new code.
by mhh__ 9y ago
For reference: In D, you could just take a HTML parser then run it at compile time without writing any new code.
- reikonomusha 9y agoLikewise in Common Lisp, arguably much more easily.
- systems 9y agohow ... macros?
- stevelosh 9y agoVanilla macros are one option. (defmacro html (string) (some-html-parser-library:parse string)) Or you could use a function and a compiler macro to make it more of an optimization -- if the argument is known at compile-time just parse it then, otherwise wait til runtime: (defun html (string) (some-html-parser-library:parse string)) (define-compiler-macro html (&whole form string) (if (constantp string) `',(some-html-parser-library:parse string) form)) Actual example, using `string-upcase` to stand in for an HTML parsing library: (defun html (string) (string-upcase string)) (define-compiler-macro html (&whole form string) (if (constantp string) `',(string-upcase string) form)) (defun foo (arg) (print (html arg)) (print (html "compile-time")) nil) (foo "run-time") ; "RUN-TIME" ; "COMPILE-TIME" (disassemble 'foo) ; disassembly for FOO ; Size: 128 bytes. Origin: #x10106A207D ; 7D: 498B4C2460 MOV RCX, [R12+96] ; thread.binding-stack-pointer ; no-arg-parsing entry point ; 82: 48894DF8 MOV [RBP-8], RCX ; 86: 488D5C24F0 LEA RBX, [RSP-16] ; 8B: 4883EC18 SUB RSP, 24 ; 8F: 488B55F0 MOV RDX, [RBP-16] ; 93: 488B0576FFFFFF MOV RAX, [RIP-138] ; #<SB-KERNEL:FDEFN HTML> ; 9A: B902000000 MOV ECX, 2 ; 9F: 48892B MOV [RBX], RBP ; A2: 488BEB MOV RBP, RBX ; A5: FF5009 CALL QWORD PTR [RAX+9] ; A8: 480F42E3 CMOVB RSP, RBX ; AC: 488D5C24F0 LEA RBX, [RSP-16] ; B1: 4883EC18 SUB RSP, 24 ; B5: 488B055CFFFFFF MOV RAX, [RIP-164] ; #<SB-KERNEL:FDEFN COMMON-LISP:PRINT> ; BC: B902000000 MOV ECX, 2 ; C1: 48892B MOV [RBX], RBP ; C4: 488BEB MOV RBP, RBX ; C7: FF5009 CALL QWORD PTR [RAX+9] ; CA: 488D5C24F0 LEA RBX, [RSP-16] ; CF: 4883EC18 SUB RSP, 24 ; D3: 488B1546FFFFFF MOV RDX, [RIP-186] ; "COMPILE-TIME" ; DA: 488B0537FFFFFF MOV RAX, [RIP-201] ; #<SB-KERNEL:FDEFN COMMON-LISP:PRINT> ; E1: B902000000 MOV ECX, 2 ; E6: 48892B MOV [RBX], RBP ; E9: 488BEB MOV RBP, RBX ; EC: FF5009 CALL QWORD PTR [RAX+9] ; EF: BA17001020 MOV EDX, 537919511 ; F4: 488BE5 MOV RSP, RBP ; F7: F8 CLC ; F8: 5D POP RBP ; F9: C3 RET ; FA: 0F0B10 BREAK 16 ; Invalid argument count trap `html` is only called once, to handle the call that isn't known at compile time.
- TeMPOraL 9y agoMacros, or (eval-when (:compile-toplevel) [your code here]). Caveats apply.
- mhh__ 9y agoThere is no macro needed here. You just write the code, then execute it at compile time. This is designed properly, it's not any where near as hacky as C++'s constexpr
- junke 9y agoNo need for macros, eval-when is a special operator designed for this: (eval-when (:compile-toplevel) ...) You can also have read-time macros or load-time values, depending on what you need.
- rep_movsd 9y agoWell LISP has no distinction between meta-programming and programming. so as long as you like parens, you can do anything
- fooker 9y agoOut of curiosity, is it possible to debug that in compile time?
- giancarlostoro 9y agoWith Vibe.d you can use Pug / Jade templates and they will be parsed at compile time so you don't have to interpret them at run time.
- rep_movsd 9y agoYes - D is what C++ should have been. By C++ 23, we will be about 80% there :| Considering that one of the greatest C++ programmers of all time (Andrei) is now a D person, that's proof enough. But for some reason, this sort of C++ shenanigan is intensely satisfying to me. I guess it's a narrow complexity fetish.
- int_19h 9y agoCan D be used without GC? (Note, by "used" here I mean utilizing most of the language, and the full ecosysstem of libraries, or at least most of it; not a mode that is supported in theory but useless in practice.)
- dawg 9y agoYes, if you're willing to spent some effort on it. Somewhat simpler you can just avoid most GC allocations so you don't run into any performance issues with the GC. http://dlang.org/blog/the-gc-series/ http://dlang.org/blog/the-gc-series/ Mind to share why a GC seems to be unaccceptable for you?
- tjoff 9y agoWriting in languages with a GC is quite cumbersome. Unless you are writing a proof of concept without a care in the world for your code you still need to reason about memory just the same as in a language without a GC. Only problem is that you constantly have to fight the GC and you don't get any help from the language. And at the same time you loose valuable constructs such as RAII - for no good reason. Similar to how static language are gaining I think that we are going to realize that garbage collection has been a huge mistake. It is such a relief that we now got Rust, and the lost opportunity that is Go is nothing but tragic.
- mhh__ 9y ago> Writing in languages with a GC is quite cumbersome. On the contrary, the GC simplifies program for the vast majority of use cases. If it becomes a problem, then don't use it. > And at the same time you loose valuable constructs such as RAII. Forgive me for being argumentative, but have you looked at the D website? D has RAII, as advertised on the website homepage.
- otabdeveloper1 9y agoThat negates the whole point of templates and constexpr -- they're purely functional subsets and explicitly designed to be so. (You can argue that purely functional code is useless in real life and that C++ shouldn't strive to be purely functional, but that's another argument.)
- gpderetta 9y agoC++11 constexpr where purely functional, C++14 adds (controlled) mutation.
- p0nce 9y agoYes. We parse JSON at compile-time with std.json (in D standard library). It probably wasn't even designed with that goal. From a D point of view, compile-time parsers are almost boring since anyone can write them.