4 ms·
Popular languages that went for strict 1:1 mapping between modules and filesystem, like Java and Python, often end up moving away from it, or at least adding va
by int_19h 4y ago
Popular languages that went for strict 1:1 mapping between modules and filesystem, like Java and Python, often end up moving away from it, or at least adding various hacks (e.g. the way you can split submodules across packages in Python).
- dureuill 4y agoI don't know about Java, but in Python, 99% of the modules I create respect the 1:1 mapping between modules and filesystem. Same in Rust, the overwhelming majority of modules I create is in the standard filesystem <-> modules mapping. For generated code, I use the special syntax that allows not respecting this mapping, but that's once in a blue moon. IMO, C++ should have taken the same steps: providing sane, correct and easy defaults, while allowing the flexibility to override them when necessary (with special annotations). I'm disappointed that a modern C++ feature was designed in the long tradition of having bad defaults instead.