Issues with dual-port network card. It failed while trying to get Netgear wifi VLANs working, and now seems permanently buggered.
Advice here for compiling up a replacement driver: https://ubuntuforums.org/showthread.php?t=1022411 (dates from 2008!)
…And actually it looks like the version in Debian Squeeze is supposed to be stable/fixed. Drteeth has the next version after Squeeze. So maybe the card is just buggered. Might be cheaper to buy a new one.
Wireless Access Point
After all the arsing around with the NetGear router, in retrospect I should have bought one of these: http://static.tp-link.com/res/down/doc/Datasheet-AP500.pdf TPLink AP500: access point like the one I have downstairs, with similar feature-set. Would have knocked a few days of effort off, and operated pretty seamlessly with the other AP.
It’s Marching Season in Glasgow.
I’ve described some design requirements for implementing non-nullable and explicitly-nullable reference types in C#, and a design which meets those requirements.
However, there are two major items I’ve not yet discussed: how these null-aware types interact with .NET generic types, and how they interact with legacy code containing implicitly-null reference types.
In this episode, Generics:
In this series so far:
- Some requirements for null-aware types in C#
- A basic design
- (This article) A wee digression
- (Next time) How the design affects generic types
- (Probably) Compatibility
- (Probably) The Future
In this article we’ll digress about default values…
In my previous post, I outlined a list of requirements for non-nullable (and explicitly-nullable) reference types in C#. In this post we’ll dive into some further design decisions. Subsequent posts will look at the impact on generic types, plus backward-compatibility and some corner cases.
Expanding the type system
We add two new main concepts to the type system:
- non-null reference types T, denoted as ‘T!’, and
- explicitly-nullable reference types, ‘T?’.