amusecode
amusifier should comment code with a warning
Is your feature request related to a problem? Please describe.
it's a common practice to label code that is generated with a message to that effect, at the same time reminding users how it should be updated. basic sherlock technique. it leaves breadcrumbs.
Describe the solution you'd like
a comment line added to the code who created it
Describe alternatives you've considered
alternatively readers find out code was not under git control, so they're just shaking their head
Additional context Add any other context or logfiles about the feature request here.
Could you explain which generated code you encountered? AMUSE has code that gets generated every time again at compile time, and code that gets generated once as a starting point for the user, and which is never regenerated.
If you can explain a bit more about what you were doing and what you were expecting then that would help, as it is I don't understand what needs to be done to fix this.
I was watching in the bhtree community code, and found two files "worker_code" (cc and h) that were not in git. this is where the first line should report it was generated by a code, ideally even which command line options. great for Sherlockians.
autoconf does something similar when it converts the configure.ac file into configure.
I had a quick peak at the amusifier code, but couldn't get enough traction fast enough.
Yeah, that code is messy, lots of fixed things that should probably just be in a library, it's needlessly object oriented, and so on. I've rewritten src/amuse/rfi/tools/create_dir.py but refactoring the rest (or even the whole RFI layer) is a whole other project I fear.
I still need to write documentation on how to set up the new build system when adding a new code, and that would explain these files at least.
It's clear what the problem is now, thanks!