Timeline for Object oriented design for access control
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2017 at 9:34 | comment | added | Mike Baxter | @Tommy No. This is a code review site and thus primarily opinion-based. I'm not sure why you're expecting me to provide 'evidence' when you yourself haven't provided any in your original answer - an answer that is entirely opinion-based. | |
| Jul 7, 2017 at 8:11 | comment | added | Vogel612 | @Tommy it's very poor practice, because it means the calling code has no specific information as to which exceptions are thrown. That's a problem, because specialized Exception types do contain additional information, which can't be recovered without guessing their type, making the whole exercise a problem... | |
| Jul 7, 2017 at 0:41 | comment | added | CodingNinja | @Teifi "Stating "throws Exception" for a method I think is poor practice..." do you have some evidence to back that up? it sounds more like an opinion to me, rather than a fact. | |
| Jul 7, 2017 at 0:39 | comment | added | CodingNinja | @Vogel612 it just shortens code, while producing the same effect. | |
| Jul 6, 2017 at 12:56 | comment | added | Mike Baxter |
All good points except for the last one. Stating "throws Exception" for a method I think is poor practice, as you should never really be throwing a raw 'Exception', rather a sub-class of an exception that describes what the problem actually is. I would recommend something like UserNotValidException.
|
|
| Jul 6, 2017 at 8:49 | comment | added | Vogel612 | I don't understand where the last point comes from ... | |
| Jul 6, 2017 at 5:46 | history | answered | CodingNinja | CC BY-SA 3.0 |