True when a language derives its module from the CONTAINING DIRECTORY (Java package, Go package) rather than baking the filename stem into the module QN. For these languages a sibling file in the same dir shares the module, and the type/method name is appended once — so a class `Outer` in `Outer.java` is `proj.Outer`, not `proj.Outer.Outer`, and a method in `myapp/db/conn.go` belongs to module `pr
| 1263 | // `proj.Outer`, not `proj.Outer.Outer`, and a method in `myapp/db/conn.go` |
| 1264 | // belongs to module `proj.myapp.db`, not `proj.myapp.db.conn`. |
| 1265 | static bool cbm_lang_module_is_dir(CBMLanguage lang) { |
| 1266 | return lang == CBM_LANG_JAVA || lang == CBM_LANG_GO; |
| 1267 | } |
| 1268 | |
| 1269 | char *cbm_fqn_module_source_lang(CBMArena *a, const char *project, const char *rel_path, |
| 1270 | CBMLanguage lang) { |
no outgoing calls
no test coverage detected