1,079
edits
Difference between revisions of "Modular Backends"
Jump to navigation
Jump to search
→Source layout
(Added notes on we could organize the source.) |
|||
| Line 53: | Line 53: | ||
* <code>backends/fs/..</code> | * <code>backends/fs/..</code> | ||
* <code>backends/saves/default</code> | * <code>backends/saves/default</code> | ||
* <code>backends/saves/psp</code> | * <code>backends/saves/psp</code> | ||
* <code>backends/timer/default</code> | * <code>backends/timer/default</code> | ||
| Line 66: | Line 65: | ||
I don't want to be too strict on how far we use subdirs or not. E.g. <code>backends/midi</code> currently does not use subdirs. And the subdirs in <code>backends/fs</code> are not really needed either, since each implementation so far consists of a single source file only, so we might want to flatten it. Those are fine details we still can decide (and change) latter. | I don't want to be too strict on how far we use subdirs or not. E.g. <code>backends/midi</code> currently does not use subdirs. And the subdirs in <code>backends/fs</code> are not really needed either, since each implementation so far consists of a single source file only, so we might want to flatten it. Those are fine details we still can decide (and change) latter. | ||
The point of keeping a "platforms" directory is to allow backends to stay monolithic if they prefer: If, for example, it's easier for the DC backend to stay in a single file, then it shall be able to do so. Adding subdirs to the backends/MODULE/ dirs is mostly interesting if those are likely to be reused (but of course porters are welcome to do this separation anyway if they like to). | |||
== External Links == | == External Links == | ||