StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14867196
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-14T03:13:41.863
FavoriteCount
0
LastActivityDate
2013-02-14T03:13:41.863
LastEditDate
LastEditorUserId
0
OwnerUserId
920669
ParentId
14865478
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
A few people have suggested using the call stack to get the module information. If you want to get the type of object that made the call, it's not too bad. Unfortunately there is no feasible (ie: simple, portable and functional) method to extract instance information from data in the call stack. There are several reasons why, including problems with optimization inlining methods that then do not show on the stack... which can interfere with calling type detection as well. Given this fact, the short answer is that you have to provide a <code>Module</code> object as a parameter to the methods you are calling in the DLL. The method suggested by @p.s.w.g is one way of achieving this, but has the disadvantage of potentially polluting the symbol space of the <code>Module</code> class. This can be solved by having the <code>Module</code> class implement a protected or public API member that exposes the functions you want to provide: <pre><code>public abstract class Module { internal int ID; public class APIWrapper { Module module; public APIWrapper(Module module) { this.module = module; } public void method1() { apiimpl.method1(this.module); } public int method2() { return apiimpl.method2(this.module); } } public readonly APIWrapper API; public Module() { ID = generate_module_identity(); API = new APIWrapper(this); } public abstract void ModuleStart(); } internal static class apiimpl { public static void method1(Module module) { ... } public static int method2(Module module) { ... } } </code></pre> The other developers can then use it this way: <pre><code>class MyModule : Module { public override void ModuleStart() { API.method1(); } } </code></pre> This encapsulates the methods that your DLL exposes, without introducing too much pollution of the symbol space of the <code>Module</code> class hierarchy. [opinion type="my" value="YMMV"] However, I suggest that you seriously reconsider using this type of abstraction. If the methods you are calling require some information about the specific <code>Module</code> instance that is calling them, it should be clear in the method's parameters. Encouraging your team to follow guidelines that lead to clarity can be more important than finding ways to abstract away small details. [/opinion]
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGet a reference to the object that called a method?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCorey
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. This table or related slice is empty.
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.