Pseudocode in the wikipedia

The free wikipedia is adopting a standard pseudocode:
http://en.wikipedia.org/wiki/Wikipedia_talk:Wikicode/Specification

MShonle says something nice:
I support the idea of wikicode. Basically I think we should present
code in a Python-like language that doesn't carry so much baggage. For
example, we can use English sentences (or sentence fragments) instead
of requiring the reader to understand some obscure Python library.
(Further, Python has the baggage that there are no block-terminators:
i.e., no "}" or "end"s or "fi"s or "repeat"s. By adding such
terminators, we can make it a lot less ambiguous to all readers.) In
otherwords, we're basically right on track: removing the quirks of
Python, and making it higher-level.

Bearophile

.

Relevant Pages

  • Re: Popular bug in implementation?
    ... Cycle detection means that every substructure in the object being ... reference to a neighboring or parent structure. ... how do you turn that detection /off/ in Python? ... The reader performs ...
    (comp.lang.lisp)
  • Re: Pseudocode in the wikipedia
    ... > The free wikipedia is adopting a standard pseudocode: ... Calling a feature 'baggage' is not especially nice. ... > of requiring the reader to understand some obscure Python library. ... Python does too have block terminators. ...
    (comp.lang.python)
  • Re: Limits of the Redefinition of Lisp Syntax
    ... detects an indent or dedent like Python does? ... The problem is that the meaning of the colon ... character is hard-coded deep within the reader and is impossible to ... Note that all those colons and commas don't really add any information, ...
    (comp.lang.lisp)
  • Re: python on Mac
    ... Now I have IDLE, which runs ... 2.4.1, but typing "python" at a terminal still opens 2.3.5, because it ... Appearantly this is because it is impossible to soft wrap text on the reader side, annoying NNTP veterans everywhere--we just can't count on this hard to program behavior in most mail readers because its so impossible to program for. ...
    (comp.lang.python)
  • Re: Considering Lisp for project but not sure if it fits
    ... > CLOS is cool, but you are not coming from an OO background it seems, ... > there is not much baggage to forget. ... Python is doing that for me. ... I wouldn't mind emulating that ...
    (comp.lang.lisp)