Prev: not-reinvent-LaTeX
Up: Glasgow-NON-objectives
Top: Top
0.1.2.2. An un-emphasis on code-reordering
Some programming languages have a narrow-minded idea about what order
the pieces of a program must be presented (e.g., COBOL: identification
division, then file division, then data division [how many of you knew
this :-]), and some literate-programming systems provide lots of
machinery to get around this orderly intransigence.
We write in Haskell, which is relatively open-minded about the
order in which functions, etc., are presented. Re-splicing together
code from dispersed program fragments doesn't buy you much -- and we
think the same is true for most modern or semi-modern programming
languages. Therefore, this system has only primitive support for
reordering code.