code is data

[bruno at modulix]

Ravi Teja wrote:

(snip)
> Annoted variables, symbols and code
> layout visually cue more efficiently to the object nature than do
> explicit text definitions. Of course, this is only sensible when there
> aren't too many of any of those. In that case, the cognitive cost of
> notation outweighs the representational cost of text.
> 
> Representational minimalism is troublesome in general code (ala Perl),
> but not so in a DSL where the context is constrained.

This still impose the need to learn a new language.

> I would also like to symbolize field types since they occur so commonly
> in a definition file and only a few of them are commonly used. I admit
> though that I find the code below a bit visually jarring and I might
> use something else. But it serves to illustrate the point. I chose the
> respective symbols based on their colloquial use and association with
> the field types.
> 
> @Poll:
>     $question: length 200
>     %pub_date('date published')
> 
> @Choice:
>     poll -> Poll
>     $choice: length 200
>     #votes

<IMHO>Yuck</IMHO>.


-- 
bruno desthuilliers
python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for
p in 'onurb at xiludom.gro'.split('@')])"