Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>To expand on Jan's answer, you would have a function like:</p> <pre><code>bool my_parser(const parser_options &amp;options); </code></pre> <p>The <code>parser_options</code> type can be a simple structure, e.g.:</p> <pre><code>struct parser_options { FILE *source_file; bool warnings_as_errors; std::shared_ptr&lt;error_handler&gt; eh; ... }; </code></pre> <p>The <code>error_handler</code> can be defined like this:</p> <pre><code>struct error_handler { virtual void error(int code, const char *message) = 0; virtual void warning(int code, const char *message) = 0; virtual ~error_handler() {} }; </code></pre> <p>The program would then do something like:</p> <pre><code>int main(int argc, const char *argv) { parser_options options; // process argc/argv options here, adding them to options, e.g.: // case WARN_AS_ERROR: options.warnings_as_errors = true; break; return my_parser(options, &amp;error) ? ERROR_SUCCESS : ERROR_FAILURE; } </code></pre> <p>This allows you to write tests that call <code>my_parser</code> directly, setting up <code>parser_options</code> independently of the command line handling and allows for a different <code>error_handler</code> to be specified (e.g. one that formats the information in a form that is machine readable).</p> <p>NOTE: This is not meant to be a perfect design of a parser, it is just an example of how something like this can be designed.</p> <p>NOTE: This design is not strictly necessary for testing, providing that the application can be configured to control the pipeline (e.g. no optimization, printing internal AST, internal representation, assembly code, preprocessor output). However, the design is more flexible as it allows different programs to use it without calling the command line program directly (GUI application/IDE, static analysis tools, etc.).</p>
    singulars
    1. This table or related slice is empty.
    1. POC++ option/long option implementation
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USreece
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThere are quite a number of classes involves in the parser application. So with this approach, I have to pass options to every classes explicitly in the application? This will require some effort to refactor the classes.
      singulars
      1. PO
      1. USK Hein
    2. COYou could pass the options to every class in the application, or you can only pass what you need (e.g. the code generation classes do not need parsing options). You could use bitflags for lots of bool options. Designing a good architecture is complex. You will likely go through several iterations to get it right. Start on the leaf classes, add tests for them and build upward. It will take time, but will be worth it. You should really be iteratively improving the design, focusing on specific areas, using your experience from what you have written, what does not quite work or is hard to update.
      singulars
      1. PO
      1. USreece
 

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