New answers tagged

2

Generally speaking, including extra header files shouldn't increase the size or impact the performance of your compiled code, but it's still a very bad practice. When you're working on a project that has hundreds or thousands of source files, you want to rebuild as few files as possible when making a change to a header file. If every source file includes ...


1

If you're talking of C or C++, then no - all that happens is that your compile time is slowed as the compiler has to read and parse all the extra header files. This can be significant, especially if headers include other headers that include.. you get the idea. Compilation time can increase dramatically (so much so that some compilers like visual studios ...


1

As I understand your question, this is the Bridge Pattern. See https://en.m.wikipedia.org/wiki/Bridge_pattern "The bridge pattern is a design pattern used in software engineering which is meant to "decouple an abstraction from its implementation so that the two can vary independently".[1] The bridge uses encapsulation, aggregation, and can use inheritance ...


1

That's the Strategy Pattern. If you're looking for names, I'd suggest CrawlerStrategy JsoupCrawlerStrategy JauntCrawlerStrategy Actually, I'd go with ICrawlerStrategy, but that's just because I'm a .Net dev. :)


1

From official Erlang Programming Rules: Function names: The function name must agree exactly with what the function does. It should return the kind of arguments implied by the function name. It should not surprise the reader. Use conventional names for conventional functions (start, stop, init, main_loop). Functions in different modules that ...



Top 50 recent answers are included