Timeline for Code that reads/writes to bytes of an ascii-encoded hex string
Current License: CC BY-SA 4.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 8, 2019 at 17:02 | answer | added | Dmitry Nogin | timeline score: 3 | |
| Oct 8, 2019 at 6:17 | answer | added | Minh Tran | timeline score: 1 | |
| Oct 7, 2019 at 16:09 | answer | added | Minh Tran | timeline score: 4 | |
| Oct 6, 2019 at 17:17 | vote | accept | Minh Tran | ||
| Oct 6, 2019 at 16:39 | comment | added | dfhwze | I rollbacked your latest edit. After an answer is made, you should not edit the question anymore. This to avoid answer invalidation. | |
| Oct 6, 2019 at 16:38 | history | rollback | dfhwze |
Rollback to Revision 6
|
|
| Oct 6, 2019 at 16:08 | history | edited | Minh Tran | CC BY-SA 4.0 |
Included code excerpt in design section
|
| Oct 6, 2019 at 12:28 | history | edited | dfhwze |
edited tags
|
|
| Oct 6, 2019 at 12:10 | answer | added | user73941 | timeline score: 7 | |
| Oct 4, 2019 at 20:19 | comment | added | Minh Tran |
@t3chb0t It's a valid concern. The switch/goto pattern used here is a step towards cutting down repetition and improving readability. Ultimately, it was used as a substitute for "method extraction" because the number of cases is small. If the binary specification called for hundreds of fields, I'd convert it to a function. I hope the flow of execution is self-evident: exactly 1 case-statement runs initially to initialize a set of variables. Execution then jumps to case that does the actual work with those variables.
|
|
| Oct 4, 2019 at 18:18 | comment | added | t3chb0t |
Oh boy, you have A LOT of gotos there o_O they are sometimes useful but they are pretty scarry here.
|
|
| Oct 4, 2019 at 18:16 | history | edited | t3chb0t | CC BY-SA 4.0 |
edited title; fixed copy/paste indentation
|
| Oct 4, 2019 at 17:45 | history | edited | Minh Tran | CC BY-SA 4.0 |
Reworded first paragraph of problem statement
|
| Oct 4, 2019 at 17:34 | comment | added | Minh Tran | They're C#'s "using alias directives" (basically type aliases) whose definition must come before namespace declarations. It's at the very top. | |
| Oct 4, 2019 at 6:00 | history | tweeted | twitter.com/StackCodeReview/status/1179999681331511296 | ||
| Oct 3, 2019 at 21:23 | history | edited | Minh Tran | CC BY-SA 4.0 |
added 165 characters in body
|
| Oct 3, 2019 at 21:14 | history | edited | Minh Tran | CC BY-SA 4.0 |
Added additional details about code design.
|
| Oct 3, 2019 at 21:10 | review | First posts | |||
| Oct 3, 2019 at 21:13 | |||||
| Oct 3, 2019 at 21:07 | history | asked | Minh Tran | CC BY-SA 4.0 |