Design pattern calling c from c3/7/2024 ![]() ![]() I refactored just over a year ago from a much messier spaghetti setup to the current multiple FSMs setup, but I still can not expect someone to be able to contribute to the codebase effectively. As I am now thinking about hiring additional developers, swapping to a singleton pattern seems like a no brainer. ![]() ![]() We are a startup and so far our current firmware has been manageable as I am the only developer working on the code. We are using a BSOM that utilises the following: Our use case is very similar to as described in the topic above. I also wanted to get feedback on using #define to make the code more readable while using Singleton based on the Application Note.īackground: So I’m finally biting off some over due code refactoring work. In particular, is what I’m doing the intended use of Singleton or if I’m over applying it. Singleton - When should they be used for good software design? TutorialsĬontinuing the discussion from New application note for using the singleton pattern:īrief: This is a fantastic guide… but I’m wondering when the Singleton pattern is best used. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |