How to easily spot a dragger

Remember when I called some “developers” draggers? Well, here is an easy tip to spot one: they say C is a bad language for compilers. I guess the best language to write a compiler is one that is near the machine code, but hey, some people may not agree. I would agree, though, that C is not very good to write a parser (which seems what the guy wanted to do, in the first place) because C is not a state machine (but you can easily write one, if you have the will.)

So, when someone starts blaming a language for his/her lack of ability to change code, you know you spotted a dragger.

4 thoughts on “How to easily spot a dragger

  1. He may be right; however, the main problem with GCC is that it’s complex and feature-driven, not exactly because it’s written in C.

  2. Let me repeat myself:

    When someone starts blaming a language for his/her lack of ability to change code, you know you spotted a dragger.

    Also, if you keep reading the thread, you’ll see that the guy points Ocaml as a perfect language because it is easy to write parsers. I did the Compilers class and I know that what a compiler must do is way more than just parsing text — actually, I would say that parsing is just 10% of a work a compiler has to do. Just because it is easy to write a parser in a language, it doesn’t mean that it is easy to write a compiler with it (which was the guy main point).

    If parsing text was all that you need to do to write a compiler, we should have a Perl compiler somewhere already — not to mention an awk compiler.

Comments are closed.