StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16491617
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-05-10T22:22:46.793
FavoriteCount
0
LastActivityDate
2013-05-11T14:48:09.077
LastEditDate
2013-05-11T14:48:09.077
LastEditorUserId
138304
OwnerUserId
138304
ParentId
16432469
PostTypeId
2
Score
11
ViewCount
0
LastEditorDisplayName
text
Body
<p>Yes, you can use:</p> <ul> <li><a href="http://antlr.org/api/Java/org/antlr/v4/runtime/UnbufferedCharStream.html" rel="noreferrer"><code>UnbufferedCharStream</code></a> for your character stream (passed to lexer)</li> <li><a href="http://antlr.org/api/Java/org/antlr/v4/runtime/UnbufferedTokenStream.html" rel="noreferrer"><code>UnbufferedTokenStream</code></a> for your token stream (passed to parser) <ul> <li>This token stream implementation doesn't differentiate on token channels, so make sure to use <code>->skip</code> instead of <code>->channel(HIDDEN)</code> as the command in your lexer rules that shouldn't be sent to the parser.</li> </ul></li> <li>Make sure to call <a href="http://antlr.org/api/Java/org/antlr/v4/runtime/Parser.html#setBuildParseTree(boolean)" rel="noreferrer"><code>setBuildParseTree(false)</code></a> on your parser or a giant parse tree will be created for the entire file.</li> </ul> <p>Edit with some additional commentary:</p> <ul> <li>I put quite a bit of work into making sure <code>UnbufferedCharStream</code> and <code>UnbufferedTokenStream</code> operate in the most "sane" manner possible, especially in relation to the <code>mark</code>, <code>release</code>, <code>seek</code>, and <code>getText</code> methods. My goal was to preserve as much of the functionality of those methods as possible without compromising the ability of the stream to release unused memory.</li> <li>ANTLR 4 allows for true unlimited lookahead. If your grammar requires lookahead to EOF to make a decision, then you would not be able to avoid loading the entire input into memory. You'll have to take great care to avoid this situation when writing your grammar.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs it possible to parse big file with ANTLR?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSam Harwell
UserOwnerUserId
1. USSam Harwell
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POIs it possible to parse big file with ANTLR?
  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.