> You could have a macro that took a filename as a parameter, read the file,
> ran it through a parser of some sort, then used the parse tree to generate
> Nim code which would be compiled into your program. It would be a lot more
> work than just making a DSL with Nim syntax, but it's an option
@dsrw
> You could have a macro that took a filename as a parameter, read the file,
> ran it through a parser of some sort, then used the parse tree to generate
> Nim code which would be compiled into your program.
Awesome, it means that Nim is a language with almost infinite possibilities.
> I
@Araq
> No as there are no reader macros in Nim but the better (IMO anyway)
> alternative is to have a compile-time parser that operators on string
> literals.
Sorry for my ignorance, I'm not a experienced Python programming, what I do is
just some tools for doing somethings in my system; can
I'm coming from Python and I would like to know about Nim and its extensibility
because I have been searching for an extensible language. I was thinking on
Common Lisp but I came across Nim and I'm really interested on it.
Has Nim all the metaprogramming features that Common Lisp has? I mean, ca
