Language author here :)
if anyone wants to learn more, we have a pretty sweet team over in #hy on freenode, and have some MLs and stuff sprinkled around.
Hy, a Lisp that compiles to Python
31–40 of 75 posts
Re: Hy, a Lisp that compiles to Python
#32Most of the programming language Y to language Z requires the user to know more Z than Y. Kind of losing the point there. Everything's not only about making points, but still...
Hy was originally a project to show "Hey, see how awesome Python & AST is!". Lisp being an easy choice to implement. Just awesome it have turned into something actually use able and fun to code with.
One use for such a thing I can think of is to use it as a reference for teaching basic parsing techniques. E.g. have a project for an undergrad course where they learn how traditional recursive descent parsing works, and then they get to implement an s-expression parser (possibly to a simplified version of the python AST).
Re: Hy, a Lisp that compiles to Python
#33Earlier quoted context omitted.
Give me a fucking break, neutering language because somebody somewhere might hypothetically be emotionally damaged by reading it is something that we can save for marketers writing bone-dry press releases. If you don't like that word, then you don't have to say it. Pestering other people for saying it is a joke. Why don't you go submit pull requests to every single fucking project using the WTFPL license while you ar…
People can complain about anything they want, just like you are, and his comment about a preferred norm doesn't constitute pestering any more than yours does.
It's not the same at all. Someone initiating an offtopic kerfuffle in a public forum is inviting responses. Hopefully the author's deletion spree was lightbulb and not just karma preservation.
Re: Hy, a Lisp that compiles to Python
#34Re: Hy, a Lisp that compiles to Python
#35Language author here :) if anyone wants to learn more, we have a pretty sweet team over in #hy on freenode, and have some MLs and stuff sprinkled around.
i'll ask you the same questions i asked the parenjs author, and which i think are pretty much faqs if you're developing a language-hosted lisp dialect. (some of them, like the
interop ones, are answered in the hy docs, but it would be nice to have a quick up-front list for reference).
* lisp-1 or lisp-2?
* scoping rules?
* 1-way or 2-way python interop?
* lisp support for python objects?
* any support for tco or loop/recur?
* reader macros?
* speed penalty relative to native python?
Re: Hy, a Lisp that compiles to Python
#36[deleted]
Can someone explain for non-native English speakers what’s the problem with “goddamn”?
It's considered profane.
Television in the United States is okay with the word 'damn', but there are people who consider the combined use with 'God' to be disrespectful to the word 'God' (and believers), stemming from the belief that many religions have that 'God' (and other synonyms) should be reserved for when a person is addressing that deity. Also, many believers consider it a faux pas to impose on the deity of their chosen religion. (Goddamn, meaning "God, please damn .." is issuing a direct command rather than asking for an assistance)
This means that often times on television the word 'Goddamn' has 'God' bleeped from it, to form 'Bleeep-damn', which is okay, apparently.
(Apparently it's not disrespectful to overwrite the deity's name/title with an obnoxious noise)
Re: Hy, a Lisp that compiles to Python
#37Language author here :) if anyone wants to learn more, we have a pretty sweet team over in #hy on freenode, and have some MLs and stuff sprinkled around.
i'll ask you the same questions i asked the parenjs author, and which i think are pretty much faqs if you're developing a language-hosted lisp dialect. (some of them, like the interop ones, are answered in the hy docs, but it would be nice to have a quick up-front list for reference). * lisp-1 or lisp-2? * scoping rules? * 1-way or 2-way python interop? * lisp support for python objects? * any support for tco or loop…
I can answer most of these just from reading the stuff linked here and educated guesses.
lisp-1, bastardized-lexical (like python, though you could create your own binding constructs with macros), 2-way, yes, yes (loop/recur, no TCO afaict or trampolining), yes, yes
Re: Hy, a Lisp that compiles to Python
#38Re: Hy, a Lisp that compiles to Python
#39Earlier quoted context omitted.
i'll ask you the same questions i asked the parenjs author, and which i think are pretty much faqs if you're developing a language-hosted lisp dialect. (some of them, like the interop ones, are answered in the hy docs, but it would be nice to have a quick up-front list for reference). * lisp-1 or lisp-2? * scoping rules? * 1-way or 2-way python interop? * lisp support for python objects? * any support for tco or loop…
I can answer most of these just from reading the stuff linked here and educated guesses. lisp-1, bastardized-lexical (like python, though you could create your own binding constructs with macros), 2-way, yes, yes (loop/recur, no TCO afaict or trampolining), yes, yes
trampolining - confirmed
Re: Hy, a Lisp that compiles to Python
#40Language author here :) if anyone wants to learn more, we have a pretty sweet team over in #hy on freenode, and have some MLs and stuff sprinkled around.
i'll ask you the same questions i asked the parenjs author, and which i think are pretty much faqs if you're developing a language-hosted lisp dialect. (some of them, like the interop ones, are answered in the hy docs, but it would be nice to have a quick up-front list for reference). * lisp-1 or lisp-2? * scoping rules? * 1-way or 2-way python interop? * lisp support for python objects? * any support for tco or loop…
* lisp-1 (Python rules)
* Python (sucks)
* 2-way
* Yep! CLOS syntax
* Yep! hy.contrib.loop - to be promoted soon
* Yep, they're OK, relies on dispatch char that's static
* Very little, actually - it compiles to (pretty sane) Python AST / Bytecode - so good pdb works to debug Hy :)