Databases
StackOverflow2013
Postsdbo
PODesign Pattern For Making An Assembler
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODesign Pattern For Making An Assembler
    primarykey
    data
    text
    <p>I'm making an 8051 assembler.</p> <p>Before everything is a tokenizer which reads next tokens, sets error flags, recognizes EOF, etc.<br> Then there is the main loop of the compiler, which reads next tokens and check for valid mnemonics:</p> <pre><code>mnemonic= NextToken(); if (mnemonic.Error) { //throw some error } else if (mnemonic.Text == "ADD") { ... } else if (mnemonic.Text == "ADDC") { ... } </code></pre> <p>And it continues to several cases. Worse than that is the code inside each case, which checks for valid parameters then converts it to compiled code. Right now it looks like this:</p> <pre><code>if (mnemonic.Text == "MOV") { arg1 = NextToken(); if (arg1.Error) { /* throw error */ break; } arg2 = NextToken(); if (arg2.Error) { /* throw error */ break; } if (arg1.Text == "A") { if (arg2.Text == "B") output &lt;&lt; 0x1234; //Example compiled code else if (arg2.Text == "@B") output &lt;&lt; 0x5678; //Example compiled code else /* throw "Invalid parameters" */ } else if (arg1.Text == "B") { if (arg2.Text == "A") output &lt;&lt; 0x9ABC; //Example compiled code else if (arg2.Text == "@A") output &lt;&lt; 0x0DEF; //Example compiled code else /* throw "Invalid parameters" */ } } </code></pre> <p>For each of the mnemonics I have to check for valid parameters then create the correct compiled code. Very similar codes for checking the valid parameters for each mnemonic repeat in each case.</p> <p>So is there a design pattern for improving this code?<br> Or simply a simpler way to implement this?</p> <p>Edit: I accepted plinth's answer, thanks to him. Still if you have ideas on this, i will be happy to learn them. Thanks all.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USHossein
    1. USHossein
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODesign Pattern For Making An Assembler
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODesign Pattern For Making An Assembler
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODesign Pattern For Making An Assembler
      1. This table or related slice is empty.
      1. VTUpMod
    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.

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