> That's a very good point. I had actually forgotten that create() isn't > called until an object is accessed for the first time. Technically, you are correct. However, the kernel library makes it so that the create function is called upon compilation, not just first access. It does this through some fancy code in the auto object.