StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14576011
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-29T05:06:18.850
FavoriteCount
0
LastActivityDate
2013-12-05T12:31:48.967
LastEditDate
2013-12-05T12:31:48.967
LastEditorUserId
392946
OwnerUserId
1566221
ParentId
14574596
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
There is this tool: <a href="http://bottlecaps.de/rr/ui" rel="nofollow">http://bottlecaps.de/rr/ui</a> but it requires EBNF. To be fair, EBNF makes the grammar much clearer, since it allows the direct representations of sequences of items which would have to be inferred from a bison source file. I believe there are tools which will attempt to do this inference, too. There's also this tool: <a href="https://github.com/tabatkins/railroad-diagrams" rel="nofollow">https://github.com/tabatkins/railroad-diagrams</a> , which requires you to supply what is, in effect, an AST of the grammar (ideally, converted as per the previous one.) This might be a better option, since you can easily produce an AST of a bison grammar using, well, bison :) and it should be easy to infer the sequence operators, or even to mark them. There are probably other tools floating around as well, but I suspect they will all have similar issues. The two tools I listed at least look nice (imo) for grammars of a normal size. You can find more links on <a href="http://en.wikipedia.org/wiki/Syntax_diagram" rel="nofollow">Wikipedia</a>. By the way, I suppose you know that recent bison version will produce <code>DOT</code> files describing the parsing states? (Use the <code>-g</code> option.) Those are of very little use for documenting grammars, and you need a lot of space if your grammar is anything approaching complicated, but they can also provide some useful information about the grammar. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAuto-Generating Syntax Diagrams from Bison
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGunther
UserOwnerUserId
1. USrici
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAuto-Generating Syntax Diagrams from Bison
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.