Reinventing the wheel, or the technology that drives it? [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 11 years ago. I recently asked a question on StackOverflow that […]
How to avoid reinventing the wheel when using complex frameworks?
For the backstory, I’m developing a GUI application in C#/WPF. I already had in my code quite many instances of
How to avoid reinventing the wheel when using complex frameworks?
For the backstory, I’m developing a GUI application in C#/WPF. I already had in my code quite many instances of
Holding of files being edited in a text editor
I’m writing an implementation of Ex (hopefully Vi eventually) as a personal project. I need to somehow store an identifier for the file associated with each buffer. In terms of security/race conditions and performance (and convention, if there is one), should I store the name of the file as given by the user, the file descriptor as returned by open(), or the file pointer as returned by fopen()/fdopen()?
Generalization of phase based systems for card and board games
In an exercise of futility I’m trying to abstract and generalize a framework where to build any turn/rule based system. I’ve had a head start but after decompiling HearthStone I’m second-guessing that it may have higher complexity than I expected, at least for abstraction. So, I would like a peer review of the approach I am taking.