StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6143383
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-05-26T18:31:12.770
FavoriteCount
0
LastActivityDate
2011-05-27T09:54:18.730
LastEditDate
2011-05-27T09:54:18.730
LastEditorUserId
10661
OwnerUserId
10661
ParentId
6143087
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The limitations of making a "mini language" have become apparent. Proper languages have a tree-like structure and more complex syntax than <code>cmd</code> can handle easily. Sometimes it's actually easier to use Python directly than it is to invent your own DSL. Currently, your DSL probably reads a script-like file of commands. Because of the way <code>cmd</code> works, your little comments get a string argument, which must be parsed. Then the command gets executed. And, further, each command is a method of the <code>cmd.Cmd</code> subclass. Here's what you can do. Each <code>do_foo( self, args )</code> method becomes a stand-alone callable object. It will follow the Command design pattern. It will do exactly what the method function does now. No less. Exactly the same. <pre><code>class Foo( object ): def __init__( self, global_context ): self.context= global_context def __call__( self, args ): ... The rest of do_foo ... </code></pre> Additionally, your existing <code>cmd.Cmd</code> subclass probably maintains some internal state. All of the <code>self.this</code> and <code>self.that</code> instance variables must be changed to reference and explicit context object. <pre><code>class Context( object ): pass </code></pre> Change <code>self.this</code> or <code>self.that</code> to <code>self.context.this</code> or <code>self.context.that</code> Now, you can create your context and your various commands. <pre><code>ctx = Context() foo= Foo(ctx) </code></pre> Your script changes syntax slightly. From: <pre><code>foo argstring bar argstring </code></pre> to: <pre><code>from mylanguage import foo, bar foo( "argstring" ) bar( "argstring" ) </code></pre> This does Exactly what the CLI does now. No more. No less. Exactly the same. Slightly different syntax. Now your script is no longer in a DSL that's hard to expand. It's in Python. Having done that, you can now use Python syntax <code>if</code> statements. You have the Exact functionality currently implemented in <code>cmd</code> with better syntax.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPython cmd interpreter adding if statements
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USS.Lott
UserOwnerUserId
1. USS.Lott
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
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.