[psas-avionics] git
Hi again all, It seems to be becoming more and more apparent that I know nothing about this git (and linux in general) thing... I seem to have lost the ability to use the psas eagle library and don't really know how to get it back. I know at the last capstone meeting I was having some problems getting connected properly (again, not all that sure why) but I seem to be connected now. How do I actually access the library in eagle? Thanks for any help! On that note when it comes to the diff thing, I'm sure I'll have tons more dumb questions, so please bear with me! =) Scott ___ psas-avionics mailing list psas-avionics@lists.psas.pdx.edu http://lists.psas.pdx.edu/mailman/listinfo/psas-avionics
[psas-avionics] code question...
So, I'm trying to compile, and I'm getting stuck with this:
main.c:200: error: expected expression before ‘signed’
---
190//there should be a few handler states...
191switch(UARTstate)
192{
193case PIPE_UARTHandlerState ://this case is to handle PIPE
UART communication
194break;
195case STANDARD_UARTHandlerState ://this case is to handle
standard UART communication
196
197//we don't want to enable output, but to send
data...
198//if( enableOutput ) { }
199
200signed portCHAR theChar;//reelin' in Chars one at a
time...
201portCHAR incomingCommand[128];//need to have a string
here to collect all them Chars... Should this be signed?
202int incomingCommandLength = 0;//this is the length of
the collected command. //sizeof() probably gets me this, and this would
then be redundant...
---
portCHAR works *all over the place*, and replacing that with char makes no
difference (iirc portCHAR == char via a #define in an obscure .h) I'm
getting the impression that it's just pissy about the case structure, but
that seems correct to me...
___
psas-avionics mailing list
psas-avionics@lists.psas.pdx.edu
http://lists.psas.pdx.edu/mailman/listinfo/psas-avionics
Re: [psas-avionics] code question...
In message 8f5d905c0904091948y526182edm16cb2bf4d5a42...@mail.gmail.com you wrote: It turns out wrapping that last case in curly-braces makes everything happy and compileable... Not that this is comfortable... It's a less-than-good feature of C. Case labels are labels, and thus must label a statement. My version of gcc gives the helpful error message error: a label can only be part of a statement and a declaration is not a statement, which pretty much summarizes the problem. Ironically, sticking a semicolon right after the colon in the case label makes it label an empty statement, making the whole thing OK again. Please don't do that. :-) In any case, as gcc says with -ansi -pedantic, warning: ISO C90 forbids mixed declarations and code. C99 does not, which is how it should have been from day 1 in the C language. Bart ___ psas-avionics mailing list psas-avionics@lists.psas.pdx.edu http://lists.psas.pdx.edu/mailman/listinfo/psas-avionics
