Some ideas: One possible legitimate use I can think of is when you want to make a function available without creating a symbol with external linkage and polluting the external namespace. (But then you could just use an obscure prefixed name like mylib123__foobar, and #define foobar mylib123__foobar in the header file, so this one seems … Read more
Even though maven projects have single parent, they can import any number of other pom’s like this: <dependencyManagement> <dependencies> <dependency> <groupId>org.example</groupId> <artifactId>my-shared-dependencies</artifactId> <version>0.0.1-SNAPSHOT</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> This has two important differences compared to a parent: Plugins defined in the imported pom won’t be imported Dependencies defined in the imported pom won’t be added … Read more
There is actually a (subtle) difference between the two. Imagine you have the following code in File1.cs: // File1.cs using System; namespace Outer.Inner { class Foo { static void Bar() { double d = Math.PI; } } } Now imagine that someone adds another file (File2.cs) to the project that looks like this: // File2.cs … Read more
In a header file you have to include ALL the headers to make it compilable. And don’t forget to use forward declarations instead of some headers. In a source file: corresponded header file necessary project headers 3rd party libraries headers standard libraries headers system headers In that order you will not miss any of your … Read more
The standard answer is to use packages — see the Writing R Extensions manual as well as different tutorials on the web. It gives you a quasi-automatic way to organize your code by topic strongly encourages you to write a help file, making you think about the interface a lot of sanity checks via R … Read more
I have just taken a C# solution and did just this (remove any file that had multiple public classes in them) and broke them out to individual files and this has made life much easier. If you have multiple public classes in a file you have a few issues: What do you name the file? … Read more
For a file module.py, the unit test should normally be called test_module.py, following Pythonic naming conventions. There are several commonly accepted places to put test_module.py: In the same directory as module.py. In ../tests/test_module.py (at the same level as the code directory). In tests/test_module.py (one level under the code directory). I prefer #1 for its simplicity … Read more
In many cases, these deeply-nested indentations are the result of deeply-nested error checking. If that’s so for you, you should look into MaybeT and its big brother ExceptT. These offer a clean way to separate the “what do we do when something went wrong” code from the “what do we do assuming everything goes right” … Read more
Used properly, this can be a useful technique. Say you have a complex, performance critical subsystem with a fairly small public interface and a lot of non-reusable implementation code. The code runs to several thousand lines, a hundred or so private functions and quite a bit of private data. If you work with non-trivial embedded … Read more
There is actually a (subtle) difference between the two. Imagine you have the following code in File1.cs: // File1.cs using System; namespace Outer.Inner { class Foo { static void Bar() { double d = Math.PI; } } } Now imagine that someone adds another file (File2.cs) to the project that looks like this: // File2.cs … Read more