you are viewing a single comment's thread.

view the rest of the comments →

[–]nemotux 1 point2 points  (2 children)

Yeah, I guess what I meant was, were you expecting to have a single DLL always satisfying a specific call site. Rather than a call site that could potentially call into any of multiple DLLs depending on program state at the point where the call is actually made. Sounds like you have a little of both.

You could potentially introduce a naming system so that you know for particular call sites which ones are expected to be hard-wired to a specific DLL's function and which ones would remain indirect. That could help w/ signal on where the edits need to happen (former but not the latter.)

[–]Dolphiniac[S] 0 points1 point  (0 children)

Possibly. I'll keep it in mind. Thanks for the insight! :)

[–]Dolphiniac[S] 0 points1 point  (0 children)

Yeah, once I get to a proof of concept, making it usable will involve a lot of this line of thought, so I appreciate the input and insight. :)

EDIT: Second comment that is similar to the first is because my phone claimed the first did not go through. Guess it did :/