Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Can all compiler errors be caught by language server?

Parent

Can all compiler errors be caught by language server?

+3
−0

Here is the reasoning:

  1. Compiler error is syntax error
  2. Language server can catch all syntax error
  3. Therefore, all compiler errors can be caught by language server

I have the feeling that this is true, based from my understanding on Language Server Protocol - Wikipedia. But the article doesn't explicitly mention any point of above.

If point 3 is true, then we can say that language server catches compiler error without having a compiler. And as the difference between an IDE and a code editor is just whether the compiler is integrated in it or not, then we can redefine IDE as a code editor with language server. Or we can say that as of today, code editor is IDE, and IDE is code editor, and we only need to use one term. The necessity for using the term IDE has ceased to exist. We only use it as a habit.

Why is VS Code considered as a code editor and not an IDE ? : r/vscode

History

0 comment threads

Post
+7
−0

Compilers raise many errors other than syntax errors.

A compiler can act as a language server and expose all of the errors it raises through that interface. Not many compilers do this yet, but in principle nothing stops them from doing so.

At our current point in history, though, a compiler is a tool whose primary responsibility is turning source code into executable code, and a language server is a tool whose primary responsibility is exposing information about symbols and errors to an editor. Nothing stops one tool from being written to fulfill both responsibilities, but they are distinct responsibilities.

History

1 comment thread

Non-syntax errors that compilers can catch (3 comments)
Non-syntax errors that compilers can catch
Ooker‭ wrote about 1 month ago · edited about 1 month ago

Compilers raise many errors other than syntax errors.

Can you elaborate this? What non-syntax errors that compilers can catch too?

Olin Lathrop‭ wrote about 1 month ago

One example is an assignment to a variable where the expression is a symbol. When that symbol is the name of a variable of the correct type, then that's fine. If the symbol is something that doesn't result in an expression or an expression of the wrong type (depending on language), then it's a compile-time error. However, it is still syntactically correct.

Ooker‭ wrote about 1 month ago

can you give an example for that example? Maybe a piece of code