Databases
StackOverflow2013
Postsdbo
POToken Attributes
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POToken Attributes
    primarykey
    data
    text
    <p>I have written simple lexical analyzer. And I understand the need to provide each recognized token with attribute. Let's see what I got:</p> <pre><code>public sealed class Token { public enum TokenClass { Identifier, StringLiteral, NumberLiteral, Operator, PunctuationSeparator, Bracket, Parenthesis } public TokenClass Class { get; internal set; } public String Value { get; internal set; } } </code></pre> <p>In lexer I enqueue tokens setting up thier value &amp; class. But what about attributes? How should I design the feature relative to my existing token class?</p> <p>First tought came into my mind was:</p> <ol> <li>Declare private abstract classes of "ambiguous-entities" (I mean that Number could be Integer and Real and so on) inside token class;</li> <li>Then declare inherited classes e.g. <code>public class Comma : PunctuationSeparator {}</code>;</li> <li>Add Property <code>Object Attribute {get; private set;}</code>;</li> <li>Then create method like <code>private void ApplyAttribute()</code>;</li> <li>Call <code>ApplyAttribute()</code> when token is instantiated and properties are set;</li> <li><p>Use something like this inside <code>ApplyAttribute()</code>.</p> <pre><code>switch(this.TokenClass) { case this.TokenClass.Number: { this.Attribute = (Int32.TryParse(this.Value))? new Integer() : new Real(); } } </code></pre></li> </ol> <p>In parser it would be easy to write something like that <code>if(CurToken.Attribute is Integer)</code>. One thing that stops me from doing like that is number of classes I should create. Is this solution acceptable?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USlexeme
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. CODo you have an ontology of your domain? It should not be the case that you have to make all different kind of empty classes. Did you already create a structure of inheritance? Maybe setting different types of `PunctuationSeperator`s is enough.
      singulars
      1. POToken Attributes
      1. USMarnix
    2. CONo I haven't yet created anything described here. These are just my plans and doubts. It seems to be useful, but ...classes... I can't decide.. help:) What do you mean saying your last sentence?
      singulars
      1. POToken Attributes
      1. USlexeme
    3. COWhen creating a class like `PunctuationSeperator`. It could be handy to define an enum in there as well, with different puctuations [comma, period, semilocon]. So first, I think you should define how your domain is, before making such a descision.
      singulars
      1. POToken Attributes
      1. USMarnix
 

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