What are some classes of code smell in J?
For clarity, "code smell" means any characteristic of source code that
indicates a potentially deeper problem. These are anti-patterns that occur at
the source code level.
The canonical example is probably duplicated code, which indicates a potential
for abstraction or merging of the repeated code. In C-like languages, deeply
nested if statements are typically considered smelly, suggesting a potential
need for better data structures, separation of mixed concerns, etc. In haskell
"boolean blindness" is another.
When writing tacit verbs, I find that trying to avoid ("), ([) or (]), and
parentheses as much as possible often helps me find better solutions. That's
what prompted this question.
Anyway, what are similar code anti-patterns in J (or APL) that have helped you
write better J by recognizing and avoiding them?
Cheers!
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
