Click here to Skip to main content
15,885,309 members

Comments by OldWiseLlama (Top 3 by date)

OldWiseLlama 1-Mar-11 0:25am View    
Deleted
It is not just the data that you deal with in the software that determines the number of classes (or other units). I have found the following principles helpful in designing systems:
- http://www.objectmentor.com/resources/articles/srp.pdf (Single Responsibility)
- http://www.objectmentor.com/resources/articles/ocp.pdf (Open-Closed)
- http://www.objectmentor.com/resources/articles/dip.pdf (Dependency Inversion)
- http://www.objectmentor.com/resources/articles/isp.pdf (Interface Segregation)

Although it might seem boring in school, drawing UML might also actually be helpful.
OldWiseLlama 17-Feb-11 0:46am View    
Deleted
Thanks. I was going for char because it's a struct and is allocated on the stack rather than heap and so yields better performance. I'll have to look into these surrogate pairs some day.
OldWiseLlama 16-Feb-11 15:12pm View    
Deleted
Reason for my vote of 2
My criticism:
Creates two new strings on every iteration (2 Substring calls).