Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>One trick I could suggest is to separate the compilation of the constructors of both, your lexer and your grammar. The easiest way to achieve this is to leave only the declaration of those constructors in their respecitive header files and to move the definition of those functions into separate translation units. For instance:</p> <p>grammar.hpp:</p> <pre><code>template &lt;typename Iterator&gt; struct grammar : qi::grammar&lt;Iterator&gt; { grammar(); // declaration only // ... }; </code></pre> <p>grammar_def.hpp:</p> <pre><code>// This file should not contain anything else. #include "grammar.hpp" // Definition of constructor. template &lt;typename Iterator&gt; grammar&lt;Iterator&gt;::grammar() { // initialize your rules here } </code></pre> <p>grammar.cpp:</p> <pre><code>// This file should not contain anything else. #include "grammar_def.hpp" // Explicitly instantiate the constructor for the iterator type // you use to invoke the grammar (here, as an example I use // std::string::const_iterator). typedef std::string::const_iterator iterator_type; template grammar&lt;iterator_type&gt;::grammar(); </code></pre> <p>Do the same thing for the lexer object.</p> <p>This approach requires a bit more work than the straight method, but it allows to distribute the memory and time requirements for the overall compilation. Another advantage of this approach is that any change in the grammar constructor does not require the recompilation of anything except the file <code>grammar.cpp</code>.</p> <p>Another advice for the lexer: try to minimize the use of <code>token_def&lt;&gt;</code> instances as much as possible. You need to use <code>token_def&lt;&gt;</code> only when you want to access the token value as an attribute during parsing. In all other cases you might get away with <code>lex::string</code> or <code>lex::char_</code> to define your tokens.</p>
    singulars
    1. This table or related slice is empty.
    1. POMinimizing boost::spirit compile times
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UShkaiser
    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
    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. VTUpMod
    1. COPlease, can you point to an example using lex::string to define a token? I get compiler errors when I simply replace token_def<> with lex::string
      singulars
      1. PO
      1. USravenspoint
    2. COIn grammar_def.hpp you write "This file should not contain anything else". What about files that might be needed for the definition (but not the declaration) of the rules, such as phoenix_core.hpp, phoenix_operator.hpp?
      singulars
      1. PO
      1. USengineerX
 

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