4 ms·
So in your scheme (no pun intended) "good" means "preserves orthogonality and easy to reason about." Most of the problems mentioned in the article have been ad
by stcredzero 17y ago
So in your scheme (no pun intended) "good" means "preserves orthogonality and easy to reason about."
Most of the problems mentioned in the article have been addressed in Smalltalk. (Not just about Macros, but about features and supporting standards. Other problems, like the minimalist precedence rules (all math operators have the same precedence) come with the language.)
- yummyfajitas 17y agoI put "bad" in quotes to indicate I'm using the same language as the author of the article. I like macros (and side effects) in spite of their dangers. I just think lisp advocates are being simplistic when they suggest macros are not more dangerous than functions (as the author of this piece does): "...in order to understand function A that uses macro B, of course you have to know what macro B means, but in order to use function C that calls function D, you have to know what function D does. Big deal."
- stcredzero 17y agoMacros are a power tool. Heck, pointers are a power tool! You can do fantastic stuff with them. You can also create a big mess, fast! Doesn't mean we should live without electric drills, just use them intelligently.
- yummyfajitas 17y agoYou seem to be arguing against a claim I didn't make. I'm not against macros or powerful language features. I simply argued against downplaying their dangers. Pointers are also a dangerous power tool. I would have objected similarly if a C advocate said this: "...in order to understand function A that acts on char * B, of course you have to know what where char * B points, but in order to use function C that references const string& D, you have to know what D contains. Big deal."
- stcredzero 17y agoNo arguments, just an observation. Sorry if it seemed like I was disagreeing.