Timeline for Different ways to distribute (embedded) C modular library
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 1, 2017 at 20:11 | vote | accept | Phalox | ||
| Dec 31, 2016 at 12:21 | history | edited | Blrfl | CC BY-SA 3.0 |
Missed a couple of words.
|
| Dec 31, 2016 at 10:53 | comment | added | Thorbjørn Ravn Andersen | See how the C processor solves this. Do the same. | |
| Dec 31, 2016 at 8:57 | comment | added | Phalox | Maybe one more clarification: while debugging, it's quite useful to know in which module you are (modularity comes with layering, which makes everything harder to follow). Any suggestions for this? | |
| Dec 31, 2016 at 8:55 | comment | added | Phalox | Awesome comment! I'll leave this question still open for a bit to see if there are more ideas though I doubt it. You've added some extra items to consider, but your case is very clear! | |
| Dec 31, 2016 at 4:38 | history | answered | Blrfl | CC BY-SA 3.0 |