290 reputation
28
bio website
location Higginsville, MO
age 28
visits member for 2 years, 11 months
seen Apr 9 at 16:43

Jan
29
awarded  Popular Question
Feb
26
awarded  Constituent
Feb
26
awarded  Caucus
Oct
28
comment How to facilitate code reviews in a small team for embedded software?
Looking at Gerrit, the biggest issue I see is that it appears to be Git only. We have about a 50/50 mix of Git and SVN.
Oct
28
comment How to facilitate code reviews in a small team for embedded software?
I agree with that red flag. This is why I've been trying to find something to make life easier when doing reviews. We do make it a point that no un-reviewed code is sent to the field, sales demos and engineering demos are a different story. Sadly the add-on support for RepositoryHosting.com is minimal.
Oct
26
answered How to facilitate code reviews in a small team for embedded software?
Jul
22
awarded  Yearling
Feb
9
awarded  Nice Question
Nov
29
accepted Do simple accessors and mutators benefit from commented block headers?
Nov
29
accepted What are the typical naming conventions for OO C public and private functions?
Oct
24
comment What are the typical naming conventions for OO C public and private functions?
Glad you touched on the fact that the symbol won't be visible outside of the compilation unit. It dawned on me after talking with some co-workers about this topic. However to clarify the private functions are not in the header file, they are declared staticly in the C file.
Oct
21
comment What are the typical naming conventions for OO C public and private functions?
@Giorgio: The point of the upper vs lower case for public and private members is so that when reviewing the code or maintaining the code it is known at a glance if its public or private without having to search for a declaration.
Oct
21
revised What are the typical naming conventions for OO C public and private functions?
removed blonde moment ooo instead of oo
Oct
21
asked What are the typical naming conventions for OO C public and private functions?
Oct
2
comment Do simple accessors and mutators benefit from commented block headers?
It is indeed an embedded application. The largest reason that moving them public is non-ideal, to me, is that I expect that the object will get heavy reuse. So for the next variant of the application my need to apply logic or latching mechanisms any time a state is changed. FYI, the previous version of this basically had the data public. It became tedious to maintain.
Oct
2
comment Do simple accessors and mutators benefit from commented block headers?
This is the approach I have taken so far. I really don't feel that the headers provide anything to code. However before dismissing them all together, I wanted to see if someone could enlighten me with a good reason for them. The college days are still fairly hardcoded (pardon the pun) in my mind regarding coding standards.
Oct
2
asked Do simple accessors and mutators benefit from commented block headers?
Sep
5
comment What is the best way to maintain software tool chains?
@Mark Booth: Does this hold true for Windows XP as well?
Sep
5
comment What is the best way to maintain software tool chains?
This could be nicely coupled with Cameyo for the IDE's so the user could just pull down the standalone IDE, checkout a compiler, run a config script and the workspace is created.... +1 Thanks for the input
Sep
5
comment What is the best way to maintain software tool chains?
I believe this solution would work for most caes, especially when using open source compilers. Sadly, the the main compiler that I use states explicitly that this type of use in not prohibited. However a VM instillation, assumed that only 1 developer is using it at a time, is acceptable.