Live data from Hacker News

Nimrod: A new approach to metaprogramming

nimrod-lang.org

51–58 of 58 posts

Re: Nimrod: A new approach to metaprogramming

#51
post #50

Nimrod is the one which is closest to my hypothetic ideal language in features.

Yes, that's what I thought, too.

My only complaint is that my internal Python (awesome) vs. JavaScript (not so awesome but becoming standard) war gets tackled from a third side now. Another language to care about - not exactly what I needed.

Having said that: Nimrod looks beautiful and maybe it's time to hop on the bandwagon.

Re: Nimrod: A new approach to metaprogramming

#52
post #9
post #8

Some very interesting features of Nimrod which I would like to emphasize: - clean Pythonic syntax (whitespace relevant but tabs are forbidden) - native Perl syntax for regular expressions (slide 42) - subrange types as in Ada - set types as in Pascal - strings as case (switch) selectors - easy C interface with automatic type conversion (only functions as parameters need additional compiler pragmas) - typed macros (te…

For embedded use it's probably ok, anywhere C is ok. It statically links the bits of the stdlib you use but dead code elimination seems to work pretty well. A simple word counting script I just wrote compiles down to about 52k on 64bit OS X. (Src: https://gist.github.com/tylereaves/7711302 )

It looks like this might rely on the GC. From the description, you can cut that out too if you handle cleanup yourself. Not sure though.

Re: Nimrod: A new approach to metaprogramming

#53
post #49

Earlier quoted context omitted.

> I am working with Nimrod right now Cool! Is what you're working on public?

Not yet. I am working on a replacement for the Asciidoc/Docbook toolchain which I am not satisfied with. It handles an extended version of Asciidoc and aims to produce code for a few output formats (HTML, TeX).

Nimrod includes rst parsing and html/tex generation (http://build.nimrod-lang.org/docs/rstgen.html). While orthogonal to your quest you may want to look into its implementation for inspiration (or adopt rst instead of asciidoc for your publishing needs).

Re: Nimrod: A new approach to metaprogramming

#55
post #49

Earlier quoted context omitted.

Not yet. I am working on a replacement for the Asciidoc/Docbook toolchain which I am not satisfied with. It handles an extended version of Asciidoc and aims to produce code for a few output formats (HTML, TeX).

Nimrod includes rst parsing and html/tex generation ( http://build.nimrod-lang.org/docs/rstgen.html ). While orthogonal to your quest you may want to look into its implementation for inspiration (or adopt rst instead of asciidoc for your publishing needs).

Interesting. I'll take a closer look at it.

Re: Nimrod: A new approach to metaprogramming

#56
post #6

This looks really neat! Looks like a cross-platform language thats an even more acceptable lisp than ruby (hello macros!), with multiple build-language targets including C/javascript/C++ and a fast garbage collector? Like Go, but even cooler?

My enthusiasm is greatly lessened. The IDE doesn't compile on Mac OS X. Even worse, the developers don't care, and keep closing the issue.

https://github.com/nimrod-code/Aporia/issues/37#ref-issue-17...

As a rule, I avoid any project where the developers have too much of the it-doesn't-work-and-I-don't-care attitude, mainly because you can't build on top of a foundation that isn't maintained fastidiously--you'll waste all your time fixing the foundation and won't get productive work done. Culture matters.

Re: Nimrod: A new approach to metaprogramming

#57
post #56
post #6

This looks really neat! Looks like a cross-platform language thats an even more acceptable lisp than ruby (hello macros!), with multiple build-language targets including C/javascript/C++ and a fast garbage collector? Like Go, but even cooler?

My enthusiasm is greatly lessened. The IDE doesn't compile on Mac OS X. Even worse, the developers don't care, and keep closing the issue. https://github.com/nimrod-code/Aporia/issues/37#ref-issue-17... As a rule, I avoid any project where the developers have too much of the it-doesn't-work-and-I-don't-care attitude, mainly because you can't build on top of a foundation that isn't maintained fastidiously--you'll wast…

Don't worry. You'd be better off using a normal text editor anyway. GTK+ is flaky on non Linux/BSD systems.

They should note what some of the OpenDylan folks are doing and write a plugin for Intellij.

Post reply on HN