I must bring again the concept of granularity. You are talking
about ortogonality of big components that you can treat as black
box objects that you access thru methods. Signatures allow to
distinguish methods by the same name.
But if you go back to the small building block of a language
the black box approach does not work. The shellish approach
used by (old Bourne shells, tcl) is to treat the langage as an empty
shell that provide little more than flow control.
The cost is the you must fork process. Also there is the problem
of multiple level of interpration agravated by the abscence of
powerful quoting mechanisms like qq||.
Language for compiled program also delegates to black box libraries. But a "real" language like perl tries to integrate
in the syntax common patterns like the use of hash.
The problem is to find enough "dimensions" in the syntax to pack
enough of this patterns in a readable way.
--
stefp -- check out TeXmacs
wiki
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.