Today I read Ten modern layouts in one line of CSS about advanced contemporary CSS features.
Today I read The End of OS X. I particularly liked the bit about the Unix philosophy:
- Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new “features”.
- Expect the output of every program to become the input to another, as yet unknown, program. Don’t clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don’t insist on interactive input.
- Design and build software, even operating systems, to be tried early, ideally within weeks. Don’t hesitate to throw away the clumsy parts and rebuild them.
- Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw some of them out after you’ve finished using them.
Found a cool series of articles: How to Build HTML Forms Right. Only the first two of five articles have been published so far, but I’m looking forward to the next three. The articles are about how to do forms right in HTML 5.
The articles are rich with links, click through for heaps of info. Some things that I found:
Today I stumbled upon GRASP. I give it a 5 out of 10.
Just stumbled upon What every programmer should know about memory:
I’ve been wondering what happens when a derived class defines a virtual destructor. What about its base destructors? Are they called? If so, when? I finally read the right paragraph in The C++ Programming Language (pg 70):
A virtual destructor is essential for an abstract class because an object of a derived class is usually manipulated through a pointer to a base class. Then, the virtual function call mechanism ensures that the proper destructor is called. That destructor then implicitly invokes the destructors of its bases and members.
Still not sure when the bases and members are destructed, presumably after the derived virtual destructor…
Am reading The C++ Programming Language, 4ed, by Bjarne Stroustrup and his sixteenth suggestion for Java programmers (pg 21) is:
A C++ nested class does not have access to an object of the enclosing class.
I didn’t know that!
Am reading The C++ Programming Language, 4ed, by Bjarne Stroustrup and his sixth suggestion for Java programmers (pg 21) is:
Remember: a variable is never implicitly a reference.
I didn’t know that!