I've changed xtimer's auto init to use snippets in order to show how this is supposed to be used.

Couldn't you just use #include "01snip.c"... and so on?

@gebart Yes, much simpler.

Nice one! :)

Fun thing to try:

# cd examples/hello-world
# echo 'puts("wooohooo!!");' > 10auto_init.c.snip
# make clean all term

I like the idea. 👍 Maybe add an underscore after the index for better readability?

I have some thoughts regarding file names:

.c.snip will confuse many IDEs which set syntax highlighting based on *.c, is it possible to fix without getting them sucked into the normal build rules?

Since the name part of NNname.c.snip is what groups them together, would it make sense to change the pattern to nameNN.c.snip to also get the files grouped together when listing files alphabetically, in case there are multiple snips in the same directory?

.c.snip will confuse many IDEs which set syntax highlighting based on *.c, is it possible to fix without getting them sucked into the normal build rules?

I thought about that, it might be possible to use make filters filters if they're called something like *.snip.c. Then we'd have to create filter rules for all filetypes, currently this would probably also work with headers.

I'll look into it...

Since the name part of NNname.c.snip is what groups them together, would it make sense to change the pattern to nameNN.c.snip to also get the files grouped together when listing files alphabetically, in case there are multiple snips in the same directory?

good idea!

Ok, the snippets are now called <filename>.snipNN.ext.

@Kijewski I tried with a '_' between snip and number, but somehow I liked it better like this. What do you think?

I'll close this in favor of a linker-script based solution.