Difference between revisions of "Holywar"
m |
m (adding template) |
||
Line 1: | Line 1: | ||
+ | {{Holywar}} | ||
The page is dedicated to holywars about Pascal language (any kind of pascal included). | The page is dedicated to holywars about Pascal language (any kind of pascal included). | ||
Revision as of 21:56, 2 March 2010
│
English (en) │
русский (ru) │
The page is dedicated to holywars about Pascal language (any kind of pascal included).
If you're Pascal developer being involved into a next flame about Pascal language, you're encouraged to use the page. Pascal has something of a stigma as an "educational, and therefore weak" language, but it has nothing in common with a real life.
Why do we use Pascal
(if you don't use (Object) Pascal, please don't edit the section)
Often programmers are free to choose their tools, especially then coding as a hobby (rather than for their living). Lots of Pascal programmers choose the language because of:
- modern Object Pascal is simply one of the most productive languages and it can be used for almost everything.
- well structured modular language
- safe and clean syntax, great for team work
- fast compile-time
- Object Pascal have really nice oop/interfaces implementation
Q&A
Q: Why there're so many limitations on what expressions i can use in "for" and "while" operators? Why can't i define a really complex type in one line?
A: to force you to create maintainable and readable code
Q: Pascal doesn't allow to specify complex types without intermediate types. I.e. "an array of pointers to a function that accepts 2 ints and returns a pointer to function that returns a float"
<c>
float (*(*a[10])(int, int))()
</c>
A: Has it any advantage to define no intermediate type? <delphi> type
TFloatRetFunc = function : single; TSomeArray = array [0..9] of function (a, b: Integer): TFloatRetFunc;
</delphi>
Advantages over C/C++
- no preprocessor (better code reading and understanding)
- no hardly readable and poorly debugged STL