That’s cool.  I am wondering if this will break the earlier versions of avr-gcc.

Would you please collect a list of API-breaking changes and build settings changes in your contribution so we have all of them on the table at once for discussion?  Thanks!

-br


On Feb 5, 2014, at 8:58 AM, Matthijs Kooijman <notifications@github.com> wrote:

> In src/bitlash-api.cpp:
> 
> > @@ -45,7 +45,7 @@
> >  //
> >  // doCommand: main entry point to execute a bitlash command
> >  //
> > -numvar doCommand(char *cmd) {
> It's the reverse. Adding const here means "doCommand will not change the string passed in". Any callers that have a non-const char* can still pass it in normally, since converting from char * to const char * is always allowed, just not the reverse.
> 
> The rationale for this change was that a literal string is also const, so a line like:
> 
> char *foo = "bar";
> results in a compiler warning (at least with -Wall).
> 
> —
> Reply to this email directly or view it on GitHub.
>