3 ms·
> So that every edit performed would result in valid syntax after they are performed. Valid syntax, not working code, not code that semantically make sense, jus
by dmitriid 9y ago
> So that every edit performed would result in valid syntax after they are performed. Valid syntax, not working code, not code that semantically make sense, just the syntax is valid within the syntax rules.
As I said. Dumb tool for basic syntax manipulation is elevated to godlike status. After which you end up with dumb statements like these:
- editor modes like paredit let you edit in terms of the structure of your code.
- your editor pane is a text editor none the less.
- the editor is textual and not structural.
- structural editors just make sure your code will parse
and other stuff that means exactly one thing: "our language doesn't have any other/proper tools, so we pretend our parens matcher is the best thing since sliced cheese".
It's just a dumb thing that selects words and matches parens. That's it.
> In that regard, it is unfair to judge Lisp's syntax before you've mastered and used it with paredit or similar structural editors.
Spare me your condescension
- didibus 9y agoAll true and factual statements. It doesn't matter if you judge them dumb or not. > and other stuff that means exactly one thing: "our language doesn't have any other/proper tools, so we pretend our parens matcher is the best thing since sliced cheese" You're operating in the hive mind mentality of us vs them. I'm talking objectively about syntax families and types of editors. You'll probably keep being downvoted as long as you continue that kind of discourse on HN. Given Lisp syntax, a structural editor adds tremendous value. Most users of Lisp syntax languages find it an invaluable tool, and would not trade it in for code refactoring tools or linters. Its okay if you disagree. Depending on the Lisp language you pick, you can also have code refactoring tools and linters if you wish. Or maybe you just don't like the features of Lisp, that's okay too, use PHP. The fact the tool is simple and easy to implement does not change its value add. Think of how awesome the invention of the wheel is, even though its quite primitive. So at this point, its hard for me to understand your disagreement. Idea's PHP editor is not a structural editor. This is not a criticism of PHP, or Idea's editor. Emacs offers structural editing of Lisp code. I personally dislike Emacs. That doesn't change the fact it supports structural editing of Lisp code. If you are curious, for example, given Clojure as the Lisp syntax language, Emacs does offer code refactoring and linting as well as structural editing. You can extract functions, auto-complete imports, rename variables, fold code blocks, have syntax errors highlighted, have certain code errors reported on the fly, jump to definition, see source and documentation, find all usage, auto-complete, snippets, auto-format, continuously run tests, debugging with breakpoints, etc. I personally don't use Emacs though, because I like mouse support and modern GUIs. So for Clojure, I prefer IntelliJ Cursive which has all those features also, and Eclipse CounterClockWise which has most of them, minus refactoring. So I'm just pointing out that even given a Lisp which has all the linting and refactoring features you talk about, how structural editing is still highly valued and one of the best feature of all of those when wanting to code with the Lisp syntax.
- lispm 9y ago> If you are curious, for example, given Clojure as the Lisp syntax language, Emacs does offer code refactoring and linting as well as structural editing. You can extract functions, auto-complete imports, rename variables, fold code blocks, have syntax errors highlighted, have certain code errors reported on the fly, jump to definition, see source and documentation, find all usage, auto-complete, snippets, auto-format, continuously run tests, debugging with breakpoints, etc. Basically the stuff Lisp IDEs had in the 70s.
- didibus 9y agoI'm unfortunatly not old enough to know. But I've heard a lot of praise for the era of Lisp machines. It's unfortunate that most of that legacy has been lost. Common Lisp doesn't actually offer that much in terms of tooling, at least, in the free department that I've tried.
- lispm 9y agoPre-Lisp-Machine IDEs were already more advanced. See for example BBN/Xerox' Interlisp mid 70s. Generally Lisp still offers a lot, but if you don't know what to look for, you might not see it even if it is before your eyes. Even though the Clojure community reimplemented much of SLIME. It also might not be important to you. Stuff like having a Lisp compiler written in Lisp, having an actual interpreter, being able to dump images, low startup times by default, break loops, readable stacktraces, type checking compilers, resumable error handling, embedding in C applications, whole-program compilers, compilers which can create C code, ...