[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
[mizar] Formatter questions
- To: mizar-forum@mizar.uwb.edu.pl
- Subject: [mizar] Formatter questions
- From: Daniel Matichuk <dmatichu@ualberta.ca>
- Date: Tue, 11 May 2010 10:00:16 -0600
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=hTjkJZ7d0vtp1ioIIt3tjwWqIscaju7ZU5s3nr++o4Bn2ze6pAuFKKdc+BQUmC0vx3 Ks2LPbGxkVV2aw+6DLdVu9/CmmkTzGL4H9V68OiUQuM8IMttmKiISWozSW/GWB1GsdyG ncvdkLtGDciakimTOEaqD/ziPJg2Su1YFiB4k=
I have a few questions about Mizar with regards to the formatter that I'm working on:
1) Is there a comprehensive list of the meanings of all the intermediate files that are generated for an article? I have some vague ideas like "parx" seems to be related to tokenization, but really I'd like a list of what each of these is for.�
2) Related to 1), is there an intermediate file that is an abstract syntax tree, or is it possible to have Mizar generate and abstract syntax tree for an article? Ideally for formatting you'd just like an AST annotated with identifiers.