Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If this is purely for your own education regarding parsing, I would suggest tacking a much smaller / easier field than HTML , CSS and JS parsing as HTML and JS both represent some really quite nasty parsing problems which even the most experienced parser writer would feel nervous tackling.</p> <p>A language based off Scheme or Basic would probably be my first pick. (A personal favourite is building a parser / interpreter as I go through <a href="http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-10.html" rel="nofollow">http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-10.html</a> )</p> <p>(Also picking up a copy of something like Modern Complier Design probably wouldn't hurt: <a href="http://rads.stackoverflow.com/amzn/click/0471976970" rel="nofollow">http://www.amazon.com/Modern-Compiler-Design-D-Grune/dp/0471976970</a> )</p> <p>If it has to be web related in order to keep your interest, I'd take a stab at doing your parser for one of the smaller web related languages such as sass ( <a href="http://sass-lang.com" rel="nofollow">http://sass-lang.com</a> )</p> <p>On the other hand, if this is something work related where you really need to parse those specific things, I'd suggest skipping the effort of writing your own parser entirely and hook into something like the Razor or Chromium libraries. </p> <p>And to directly answer at least the second half of your question: I would recommend always splitting the various phases of parsing / interpreting out as far as possible from each other.</p> <p>Each problem is difficult enough on it's own without trying to be "too smart" and attempting to combine functionality into a single sweep.</p> <p>Where ever possible I'd suggest keeping things as high level, abstract and "clean" as possible... thus construct a tree of nodes specifically for lexical parsing and another for syntactical parsing... and in the case of combined languages as HTML, CSS and JS, a different AST and parsing code for each. </p>
    singulars
    1. This table or related slice is empty.
    1. POCustom parser for HTML5 and other languages
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USlzcd
    1. USlzcd
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCustom parser for HTML5 and other languages
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for your answer. It's just educational. If you need to come to this website to ask basic questions about something that you're building at work you probably should resign. Separating the two sounds good to me. I guess I'll just have to make token categories that work for all even though some of them wouldn't be used for certain purposes - for example I can't think of a single token in HTML that starts with a digit although a JavaScript variable value might. I doesn't have to be web related to keep me interested but making a parser for C# sounds much harder and I've never heard of SASS.
      singulars
      1. PO
      1. USHelloWorld
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload