I want a 64-bit installer (as per my Release configuration), so I used <Directory Id=”ProgramFiles64Folder”> instead of ProgramFilesFolder as part of the target installation path. This article provides more information: How to: Create the Windows Installer Package for 64-bit Client Computers
A branch instruction is not inherently slower than any other instruction. However, the reason you heard that branches should avoided is because modern CPUs follow a pipeline architecture. This means that there are multiple sequential instructions being executed simultaneously. But the pipeline can only be fully utilised if it’s able to read the next instruction … Read more
Taken at face-value, it would certainly seem like RAII works against TCO. However, remember that there are a number of ways in which the compiler can “get away with it”, so to speak. The first and most obvious case is if the destructor is trivial, meaning that it is the default destructor (compiler-generated) and all … Read more
Sure thing. It knows the value of function is the same as the value it passes it, knows the definition of the function, so just replaces the definition inline and calls the function directly. I can’t think of a condition where a compiler won’t inline a one-line function call, it’s just replacing a function call … Read more
Create a pom-only (<packaging>pom</packaging>) project that has the compiler settings (and any other default settings) you want. You give treat it like any other project (release it; deploy it to your Maven repo, etc.). Put a parent declaration at the top of your pom files: <parent> <groupId><!– parent’s group id –></groupId> <artifactId><!– parent’s artifact id … Read more
These follow gcc naming conventions. c++.exe is a traditional name for the system c++ compiler g++.exe and gcc.exe are the names for the gcc compilers that compile for the “current system” mingw32-* versions are the names for the compilers that cross-compile to the “mingw” target. In this case this is the same as the system … Read more
This is correct. Your static initializers, then the static constructor is run before your standard constructor, but when it runs, it’s using new A(), so passing through your non-static constructor path. This causes the messages you see. Here is the full path of execution: When you first call var a = new A(); in your … Read more
My guess is that you have discovered a minor bug in the optimizer. There is all kinds of special-case code in there for arrays. Thanks for bringing it to my attention.
Answer derived from this blog article: So my question is what would a more traditional functional approach to parsing (i.e. few side effects) look like? Sounds like you need to separate functional (as in Lisp, Scheme, Standard ML, CAML, OCaml, F#) from purity (absence of side effects, as in Haskell) and incidental language features (algebraic … Read more
I recommend reading Generics in C#, Java, and C++: A Conversation with Anders Hejlsberg. Qn 1. How do generics get compiled by the JIT compiler? From the interview: Anders Hejlsberg: […] In the CLR [Common Language Runtime], when you compile List, or any other generic type, it compiles down to IL [Intermediate Language] and metadata … Read more