View Single Post
  #3   Spotlight this post!  
Unread 28-02-2013, 13:24
BigJ BigJ is offline
Registered User
AKA: Josh P.
FRC #1675 (Ultimate Protection Squad)
Team Role: Engineer
 
Join Date: Jan 2007
Rookie Year: 2007
Location: Milwaukee, WI
Posts: 947
BigJ has a reputation beyond reputeBigJ has a reputation beyond reputeBigJ has a reputation beyond reputeBigJ has a reputation beyond reputeBigJ has a reputation beyond reputeBigJ has a reputation beyond reputeBigJ has a reputation beyond reputeBigJ has a reputation beyond reputeBigJ has a reputation beyond reputeBigJ has a reputation beyond reputeBigJ has a reputation beyond repute
Re: Comparing performance of two sets of code

I'm not logging anywhere yet. We are implementing a central singleton-ish class that other classes push their data to, like SmartDashboard, with specific keys. Inside the class we customize the data going out to SmartDashboard and the console, and update it periodically.

We were mainly looking for a solution to chasing down println()s and SmartDashboard output statements all over the codebase.

If everything can be "logged" without a significant performance deficit it would be nice to just write the code for that and forget about it.

Logging probably isn't the best name for this but I can't think of a better one, although the class could be extended to do customized logging in the future.

Thanks, by the way, that's good to know too!

Last edited by BigJ : 28-02-2013 at 13:28.