[ivan.moony]

The reason is that I wanted to free { } for another use: embedding other languages, like js scripts for instance.

Yeah, I have a similar idea to embed js inside metafigure. I'm thinking of extending it with native assembler in the future. The idea is to have fragments of code held inside metafigure compiled to js or asm and executed on demand. Metafigure would provide a mechanism for converting any AST (abstract syntax tree) into another AST, so you can convert, say python or java to, say javascript or asm on demand.

[Zero]

I understand, so you can have the raw power of ASM and the flexibility of metafigures...


Here are the updated examples:

Code

    computers < are < 
    (
        (
            (very > good) < at <
            (
                ( following < (exact > orders) )
                =and= 
                ( handling < ((very > specific) > things) )
            )
        )
        =but=
        (
            (not > good) < at <
            (
                dealing < with <
                (                
                    (new > things) < they < haven't seen < before
                )
            )
        )
    )

Code

    ( for example ) <
    (
        (
            ( [ a | common | computer ] > program ) < can <
            (
                turn <
                [
                    a > report < of < ( names =and= (hours < worked) )
                |
                    into < paychecks < for <
                    (
                        the > workers < at < (a > company)
                    )
                ]
            )
        )
        =but=
        (
            ( [ the | same ] > program ) < could not <
            (
                answer < questions < 
                [
                    from < (an > employee)
                |
                    about < why <
                    (
                        (the > company) < will not < pay < for < (nap time)
                    )
                ]
            )
        )
    )

EDIT: typos

[spydaz]

You have made me go back to "fluent editors" description logic ... Which can be used to describe these "OWL" like structures ..   

For me too many brackets .... Woah .....