Thank you Dennis.
I don't know if this is the right place to make a comment or express an opinion, but be that as it may I have to say that gcc needs a far better error reporting mechanism. In java if the "compiler" encounters an unterminated expression at end of file, it flags it immediately. In gcc that error is held in abeyance for a huge number of lines (about 500 in my case, in multiple files) before it's manifested as something that seems completely unrelated and slightly insane. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/856d7a95-0989-49e6-8f8b-71cb7977320f%40googlegroups.com.
