Timeline for Format RGB Long as hex string in VB6
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:24 | history | edited | CommunityBot |
Commonmark migration
|
|
| Oct 17, 2018 at 18:43 | history | edited | Felix Dombek | CC BY-SA 4.0 |
sorted table
|
| Dec 23, 2016 at 14:50 | comment | added | Cody Gray | ... At the risk of sounding arrogant, I would say that my solution strikes the appropriate balance there. Anyone can understand what the code is doing, it looks like it's doing the right thing, but it isn't necessarily the fastest. Of course, there is no such thing as the "fastest" code—anything can be improved with enough effort! The only thing about the numbers that surprised me was that there wasn't more improvement seen by enabled advanced optimizations. Like you said, though, successful branch prediction is playing a huge role here, so this may not be the best general benchmark. | |
| Dec 23, 2016 at 14:48 | comment | added | Cody Gray | Thanks for putting some hard numbers to this. The rankings are almost exactly what I would have expected, which makes me feel pretty good about the performance analyzer between my ears. :-) I hadn't seen "unknown user"'s solution (very interesting); it serves as an excellent proof of the inherent inefficiency of VB 6's built-in string manipulation. You could almost certainly do even better by importing some WinAPI functions and doing all of the string manipulation that way, but you get into a very real tradeoff between readability and maintainability, vs. real-world performance benefits. | |
| Dec 23, 2016 at 3:30 | history | edited | Felix Dombek | CC BY-SA 3.0 |
added 6 characters in body
|
| Dec 23, 2016 at 3:20 | history | answered | Felix Dombek | CC BY-SA 3.0 |