Lets start a discussion ;-)
blacklisting C files looks dangerous to me.
I could imagine to blacklist jswrap*.c files, but even that, at least for me, is like a mine field.
May be we could add some more defines to remove blocks of software, like waveform
My idea was to use wildcard to remove idle/init/kill which belong to a class
We could add class to wrapper with type idle
It could be set for waveform, and would be empty for pipe.
Going through your list, I tried to get an overview what init idle and kill are used for
init looks mainly important for some boards and for net, bluetooth. There is no need to blacklist them, we already have defines for that
idle is used for waveform, serial and pipe. IMHO serial and pipe should never be blacklisted, waveform could be blacklisted
kill usage is a mix, blacklist it for waveform should cause no problem
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Lets start a discussion ;-)
blacklisting C files looks dangerous to me.
I could imagine to blacklist jswrap*.c files, but even that, at least for me, is like a mine field.
May be we could add some more defines to remove blocks of software, like waveform
My idea was to use wildcard to remove idle/init/kill which belong to a class
We could add class to wrapper with type idle
It could be set for waveform, and would be empty for pipe.
Going through your list, I tried to get an overview what init idle and kill are used for