View Single Post
  #12   Spotlight this post!  
Unread 05-02-2005, 23:20
jgannon's Avatar
jgannon jgannon is offline
I ᐸ3 Robots
AKA: Joey Gannon
no team
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Pittsburgh, PA
Posts: 1,467
jgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond repute
Re: Cannot access "double" values

Quote:
Originally Posted by Mike Betts
However, I must inquire: If someone does not read the information presented, should we help at all?
If you've read through the FIRST Q&A, you've seen that maybe 90% of the questions are answered either in the manual or in another previously-asked question. Nonetheless, somebody at FIRST takes the time to sit down and answer them all, to make sure that everyone understands that which they desire to know. Would it be better if everybody read the whole manual, and looked through all the source code? Of course. But, as long as we're here, oughtn't we help those who don't? We could try to teach them a lesson ("READ THE MANUAL OMG NOOB"), or we can give them a solution. Mark McLeod's post in this thread is an excellent example; he provided a solution. I won't hesitate to remind people to "search before your post", but at the same time, it doesn't hurt to explain why their compiler can't find adc.h, or why they can't compile code that they're keeping on their desktop.
Quote:
Originally Posted by Mike Betts
[printf] is defined (in the default code V2.4) in printf_lib.c (maybe a poor choice of file names) and supports %d, %x, %X, %u, %l and %b formats. All are integer formats
This is an excellent piece of information for this thread... though it isn't a solution, it explains why chantilly_team is encountering this problem.
Quote:
Originally Posted by Mike Betts
My issue is that people are not even looking at the code they are given.

I can understand (begrudgilngly) questioning libraries where you have no view of the source code. But to complain about source code that YOU have control over...
I see no complaints from chantilly_team with regard to IFI's implementation of printf... am I missing something? It looks like just a question to me. "IFI wrote crappy CMU camera code" is a complaint. Don't like it? Rewrite it yourself. "I can't get the IFI-provided camera code to lock onto a tetra. How can I make it work?" is a question. Since these resources are available, let's help people learn how to use them in the ways that they want (a la Mark McLeod's post).
Quote:
Originally Posted by Mike Betts
Too many people are looking for "plug and play" code... They need to realize that, in the real world, it just does not exist. In the real world, we have no IFI or Kevin Watson to give us exquisite examples of embedded programming... What we have are spec sheets, manuals and application notes... And with this, we manage to send robots to distant planets and the bottom of the ocean...
Amen. Nonetheless, guiding people in the right direction can't hurt. I'm sure that someone at NASA has pointed out something that Dave Lavery overlooked in a spec sheet or manual.
Quote:
Originally Posted by Mike Betts
I'm sorry... I'm tired and... Maybe you are right.... Maybe I should not be posting in this state...
Build season wears us all down, but when we get to Atlanta, everything regenerates, because we've been inspired.

Just the observations of a FIRSTer who has asked no shortage of stupid questions, but still ended up having my life changed by this program.
__________________
Team 1743 - The Short Circuits
2010 Pittsburgh Excellence in Design & Team Spirit Awards
2009 Pittsburgh Regional Champions (thanks to 222 and 1218)
2007 Pittsburgh Website Award
2006 Pittsburgh Regional Champions (thanks to 395 and 1038)
2006 Pittsburgh Rookie Inspiration & Highest Rookie Seed

Team 1388 - Eagle Robotics
2005 Sacramento Engineering Inspiration
2004 Curie Division Champions (thanks to 1038 and 175)
2004 Sacramento Rookie All-Star

_