mavlink/pymavlink — comment on commit 51f3d6713e9a5b94c232ab9bf9d08095a0c97866
File:  line 0
By Susurrus:

This doesn't work correctly as ```__GNUC__``` is defined by the C30 compiler. Instead blacklist ```__C30__```:
```
/*
* Provide both a blacklist and a whitelist for enabled extended messages. As these
* are large (see MAVLINK_MAX_EXTENDED_PACKET_LEN) they may not be supported on all
* compilers.
*/
//Blacklist some embedded microcontroller compilers: Microchip's C30
#if (defined __C30__)
// Whitelist other common PC compilers: GCC, Microsoft VC++, GCC, Watcom, Altium
// Microblaze C, Borland C++, Clang on LLVM
#elif (defined __GNUC__) || (defined _MSC_VER) || (defined __MINGW32__) ||
(defined __WATCOMC__) || (defined __CMB__) || (defined __BORLANDC__) ||
(defined __clang__)
#define MAVLINK_EXTENDED_MESSAGES_ENABLED
#endif
```

It would have been nice, however, if the full-feature set of MAVLink would be available on compilers with problems with this storage size. Would it be unreasonable to reduce the value of ```MAVLINK_MAX_EXTENDED_PACKET_LEN``` instead to less than 32767?