Timeline for Math expression parser in C#
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2019 at 11:29 | history | edited | dfhwze | CC BY-SA 4.0 |
typo fix
|
| Dec 11, 2014 at 21:36 | comment | added | Petrroll | BTW: Reimplementing your code I've found two issues with it: 1) it doesn't compound whitespaces 2) it breaks when a coumpoundable token follows a uncompoundable (adds an empty string). Anyway, I've added refactored version to my original message. | |
| Dec 11, 2014 at 13:20 | comment | added | Petrroll | Ok, that is kind of awesome. Truly nicely readable code. The only 'issue' I see with it is that you have to test for numbers and names when appending whitespace (and for numbers when names)... On the other hand, the performance loss is probably insignificant in comparison to the readability gain. | |
| Dec 11, 2014 at 13:05 | history | edited | Heslacher | CC BY-SA 3.0 |
deleted 25 characters in body
|
| Dec 11, 2014 at 13:04 | vote | accept | Petrroll | ||
| Dec 11, 2014 at 12:57 | history | edited | Heslacher | CC BY-SA 3.0 |
added 1493 characters in body
|
| Dec 11, 2014 at 12:32 | history | edited | Heslacher | CC BY-SA 3.0 |
added 732 characters in body
|
| Dec 11, 2014 at 12:08 | history | edited | Heslacher | CC BY-SA 3.0 |
deleted 78 characters in body
|
| Dec 11, 2014 at 11:49 | history | edited | Heslacher | CC BY-SA 3.0 |
deleted 68 characters in body
|
| Dec 11, 2014 at 11:42 | history | edited | Heslacher | CC BY-SA 3.0 |
added 3141 characters in body
|
| Dec 11, 2014 at 10:22 | comment | added | Petrroll | Good points, the question is how to implement 'names and nums' (longer elements) parsing when parseNextToken takes only char as an input. Could you explain that a bit further? | |
| Dec 11, 2014 at 9:52 | history | edited | Heslacher | CC BY-SA 3.0 |
added 621 characters in body
|
| Dec 11, 2014 at 9:44 | comment | added | Abbas | @Petrroll Methods always have PascalCasing. Only private members (not methods) or parameters use camelCase. | |
| Dec 11, 2014 at 9:18 | history | edited | Heslacher | CC BY-SA 3.0 |
deleted 47 characters in body
|
| Dec 11, 2014 at 9:18 | comment | added | Heslacher |
significantly slower is true, but what the ... using a String containing 100.000 chars will be done in 10 ms. It is for sure easier to read.
|
|
| Dec 11, 2014 at 9:01 | comment | added | Petrroll | Isn't your implementation of IsOperator significantly slower? Also, could you give me your opinion about the general class structure (E.g. using bufferPointer as whole-class variable, ...)? And lastly, shouldn't PascalCase be used only for public function (and Camel for private)? | |
| Dec 11, 2014 at 8:59 | history | answered | Heslacher | CC BY-SA 3.0 |