Timeline for Design pattern for wrapping logging around execution
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 12, 2015 at 9:54 | comment | added | Make42 | @Spotted: That would hardly make any sense. If it is as you say, I'd rather have to put the code from the constructor into a function like executeWithLogging() and cmd.executeWithLogging(). Afterall, that is what should be executed. | |
| Oct 12, 2015 at 7:42 | comment | added | Spotted | No it's not the case. You would have to write something like: MyLoggingCommandWhole cmd = new MyLoggingCommandWhole() { ... }; cmd.executeWithoutLogging(); | |
| Oct 10, 2015 at 12:07 | comment | added | Make42 | @Spotted: I thought that instaciating MyLoggingCommandWhole, executes executeWithoutLogging(); from MyLoggingCommandWhole. Is that not the case? | |
| S Oct 7, 2015 at 11:32 | history | suggested | Spotted | CC BY-SA 3.0 | fix code indentation |
| Oct 7, 2015 at 9:51 | comment | added | Spotted | Also execute() do nothing at the moment as you're just instanciating MyLoggingCommandWhole. | |
| Oct 7, 2015 at 9:50 | comment | added | Spotted | I don't have a lot of experience with the command pattern. The only obvious negativ point I see is that it's hardly readable (note the level of indentation), so I won't use it because I like to care of the people who will read my code in the future. | |
| Oct 7, 2015 at 9:46 | review | Suggested edits | |||
| S Oct 7, 2015 at 11:32 | |||||
| Oct 3, 2015 at 12:05 | history | answered | Make42 | CC BY-SA 3.0 |