Google C++ Style Guide

To select an item in a list view create an LVITEM structure, change a few of it’s fields and pass it to LVM_SETITEMSTATE:

// Select current item in the list
LVITEM item = {0};
item.mask = LVIF_STATE;
item.state = item.stateMask = LVIS_SELECTED;
SendMessage(mhProductList, LVM_SETITEMSTATE, mCurrentSettings, (LPARAM)&item);

Oh and if you’re trying to turn on whole line section you’ll need to use the extended styles:

// Set extended styles
SendMessage(hWndListView, LVM_SETEXTENDEDLISTVIEWSTYLE, 0, LVS_EX_FULLROWSELECT);

"--start-group", "--end-group", aternatively "-(" "-)"

See the man page for LD for more info

Unfortunately this argument comes with the following little warning:

Using this option has a significant performance cost. It is best to use it only when there are unavoidable circular references between two or more archives.

The particular case I was dealing with was the havok version 6 libraries on linux. I was advised that there may be way to link them but hadn’t been worked out. In order to test this theory I hacked together a little bit of ruby to show library dependencies. I feel this may be of some use to someone else so I present it here:

require 'find'

$symbs = {}
$archives = []

class Archive
    attr_reader :name, :symbs, :depends, :undef
    def initialize name
        @name = name
        @symbs = {}
        @undef = {}
        @depends = Hash.new(0)
    end

    def add_definition loc, name
        @symbs[name] = loc
        $symbs[name] = self
    end

    def add_undefined name
    @undef[name] = 0
    end

    def resolve_undefined
        @undef.each do |k,v|
            archive = $symbs[k]
           if not archive or archive == self then
                next
            end
            @undef[k] = archive
            @depends[archive] = @depends[archive] + 1
        end
    end
end

Find.find('.') do |path|
    next if not /.a$/.match(path)

    io = IO.popen("nm #{path}")
    archive = Archive.new(path)
    $archives << archive
    while (str = io.gets) do
        case str
        when /\w+\.a/
            archive = Archive.new(str)
            puts "archive: #{str}"
        when /[A-F0-9]+ [A-Za-z] \w+/
            parts = str.split
            archive.add_definition parts[0], parts[2]
        when /\s+U\s+\w+/
            archive.add_undefined str.split[1]
        end
   end
   puts "processed #{path}, #{archive.symbs.count} defined, #{archive.undef.count} undefined"
end

$archives.each do |archive|
    archive.resolve_undefined
end

$archives.sort! {|a,b| a.depends.count <=> b.depends.count }

puts "dependency list:"
$archives.each do |archive|
    puts "#{archive.name}: #{archive.depends.count}"
    archive.depends.each do |depend,count|
        puts "    #{depend.name}: #{count}"
    end
end

The final solution was to simply remove the object files from the static libraries and put them into a single combined library:

rm *.o
find . -name \*.a -exec ar x {} \;
ar rcs libHavok.a *.o
ranlib libHavok.a
rm *.o

I did end up finding a command line windows CVS client

I think what I would like to do is split my blog into micro-blog/status updates and actual blog posts. It would be ideal if I could use one interface to post to the both and have the micro-blog funnel to twitter/facebook. We’ll see if that makes sense. In the meantime I’ll just use a tag for the status updates.

About a week later I bring my machine up to notice some flashing red text in the BIOS. Once windows was up I had two drives and the nVidia tray icon was bothering me about my drives being in a ‘degraded’ state. This is just a fancy way of saying that the RAID setup failed and that I would have to choose a drive that would have the master data and rebuild the array from the BIOS. Note that nothing out of the ordinary had happened on my machine to cause this to happen. I closely examined the data, figured out which drive was on which controller port and dutifully rebuilt the array. I wasted a good evening going through this because I didn’t want to lose any data. I had some critical music data on the drive and wanted to make sure I wouldn’t lose everything. This was a night I normally would have been writing some useful code or recording some music.

To make a long story short this has happened over and over again. I have run integrity checks on the drives and they are both fine. Any time the machine crashes, the drives will go into a degraded state and require yet another manual rebuild. This of course is a complete waste of my time and really there is no excuse for a RAID solution to fail this UN-gracefully. The whole point is to keep me from having to deal with this kind of hassle. Not routinely force me to deal with it for no good reason. So here I am writing this post while I figure out again which drives have the latest files. I am done with NVIDIA SATA RAID. It is a complete and total epic fail. I would not recommend this to anyone.

Tree Structured Indexes

Design of BTRFS