As explained by Wikipedia, small-step semantics formally describe how the individual steps of a computation take place in a computer-based system. Big-step semantics describe how the overall results of the executions are obtained.
The difference between Require Import MyModule and Require Export MyModule is well explained in the modules tutorial:
If a required module depends on other modules then the latter’s are automatically required beforehand. However their contents are not automatically visible. If you want a module M required in a module N to be automatically visible when N is required, you should use Require Export M in your module N.
I read this paper on double-checked locking. It had a great discussion of the pitfalls of using this approach for implementing the Singleton Pattern. Here is a typical example of an unsafe implementation:
public static Singleton getInstance()
{
if (instance == null) {
synchronized(Singleton.class) {
if (instance == null)
instance = new Singleton();
}
}
return instance;
}
I found it interesting that Chromium developers implemented their own algorithm to replace bsdiff. I do not fully understand how (efficient) binary patching works, so this is a good starting point…
Notes from Encapsulation is not information hiding:
JML is a formal behavioral interface specification language for Java as documented in Design Contract With JML linked to from the University of Central Florida JML homepage. I read just the first half of the paper.
Welcome to Daily Ed. The purpose of this blog is to document something new that I learn each new day. I guess I view it as a test of the common idiom…