Talk:Extend your language: Difference between revisions
Content added Content deleted
(There are already examples of language extension on RC; point to example) |
(Keyword issue) |
||
Line 17: | Line 17: | ||
::::::: I hate wikitalk; I need a more convenient way to Upvote or Like points in debates like these. --[[User:Short Circuit|Michael Mol]] 19:15, 27 August 2010 (UTC) |
::::::: I hate wikitalk; I need a more convenient way to Upvote or Like points in debates like these. --[[User:Short Circuit|Michael Mol]] 19:15, 27 August 2010 (UTC) |
||
:::::::: If you upvote or give like points, it's not a debate any more. --[[User:Ce|Ce]] 20:58, 27 August 2010 (UTC) |
:::::::: If you upvote or give like points, it's not a debate any more. --[[User:Ce|Ce]] 20:58, 27 August 2010 (UTC) |
||
:::: IMHO, "create a keyword" would not be optimal. In languages where those extensions are a natural programming style, the term "keyword" is seldom used. Also, "extending the language" then almost always involves flow control in some way, which needs not to be mentioned specifically. |
|||
:::: For example, the typical case of a domain specific language extension like a HTML library, where a syntax like (please allow me to stay with Lisp syntax) <lang PicoLisp>(<div> |
|||
(<head> (build-the-header)) |
|||
(<p> (get-some-text)) |
|||
(<table> (make-table-header) |
|||
(for X (foo) |
|||
(<row> (row-data X)) ) ) )</lang> ''also'' involves flow control, but the central issue is structured output. Still I would call this a language extension. |