I'm looking to make/post an example Arduino tupfile, and I want to make it super well documented for new folks, so that difference between it and crappy makefiles is VERY apparent.
Unfortunately, this means over commenting. To this sort of level: FLAGS += -g # Include debug info FLAGS += -Os # Compile optimizing size FLAGS += -Wall # turn on compiler warnings Which works, cause it's neat and easy to visually scan. Unfortunately, tup doesn't support that (yet?) Instead, I'm forced into the following: # Include debug info FLAGS += -g # Compile optimizing size FLAGS += -Os # turn on compiler warnings FLAGS += -Wall Which is visually jarring, and would be offputting to new folks. Heck, it's offputting to me. I assume the lack has to do with either developer time, or minimizing escape characters. If it's escape characters, why don't we do something like: | FLAGS += -g # Include debug info Where we start the line with | to explicitly turn on inline commenting. Is there a reason not to implement this/a way that I could get this implemented? I'm willing to code, if I have buyin/someone pointing me in the right direction. -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
