freenode/#lisp - IRC Chatlog
Search
12:35:20
Shinmera
As p_l suggested, if the DWARF doesn't influence the produced binary, one aspect instead of replicating a compiler would be to parse out the DWARF info and use that to feed the information needed to call methods.
18:33:16
senecaty
Why does my isprime function always return nil? https://bpaste.net/show/1af47b67733a
18:59:38
aeth
What channel is it? Have they heard the "get a link via IRC bot that gives you a cookie, and that's the only way to paste" idea yet?
0:18:43
aeth
asarch: C++ pretends that it's on the low-level side of the high-level languages, but it has high-level syntax, which makes metaprogramming painful. It also inherits all of the security/safety flaws of C by being compatible with C.
0:21:29
aeth
Lisp doesn't force a high-level infix string representation of source code on top of the abstract syntax tree that's underneath, which makes things like macros actually doable.
0:25:07
aeth
Templates, C-style macros (i.e. string macros), and other generic/template/macro systems tend to be complicated, hard, painful, and easy to make mistakes in. Lisp-style macros (i.e. structural macros) avoid most of those issues.
0:27:25
aeth
e.g. If you need to interface with something that expects some string format, you can just write a CL macro to generate a string. Doing so is very similar to writing a function, but it will produce a string at macro-expansion-time, which can mean that string will be compiled into the native compiled form (usually a FASL file).