Weekly edition	Kernel	Security	Distributions	Contact Us	Search
Archives	Calendar	Subscribe	Write for LWN	LWN.net FAQ	Sponsors

Object-oriented design patterns in the kernel, part 1

Posted Jun 2, 2011 2:19 UTC (Thu) by cmccabe (subscriber, #60281)
Parent article: Object-oriented design patterns in the kernel, part 1

This was an interesting article. I was always curious about the use of NULL in kernel vtable structures.

The idea of associating multiple vtables with a single object-- to collect related functionality-- reminds me of Google Go's structural subtyping. Why force all the class methods to be in one .h or .java file? We should be able to group the methods in whatever way makes the most sense.

(Log in to post comments)

Ah, Google Go

Posted Jun 5, 2011 11:23 UTC (Sun) by khim (subscriber, #9252) [Link]

Well, the Google Go structural subtyping is crippled and limited version of ages old idiom.

Of course it does not mean Google Go is bad language: it's version is simpler and less flexible - but as consequence it's less dangerous too. But still... it's funny how people are becoming excited when fashionable language presets something from languge veteran they forever disliked for some reason.

Ah, Google Go

Posted Jun 16, 2011 0:15 UTC (Thu) by cmccabe (subscriber, #60281) [Link]

There have been a lot of dynamically typed languages in recent years that have implemented what's called "duck typing." Python and Ruby come to mind, but I'm sure there are others. What is different about Google Go is that it is statically typed. Common Lisp is dynamically typed.