Hives, keys, values, types, and data.<\/p>\n
As I noted some years ago, the file that holds the registry data is called a hive<\/i><\/a>. <\/p>\n A hive contains a tree of keys<\/i>. <\/p>\n Keys contain a list of values<\/i>. <\/p>\n Associated with each value is a type<\/i> and data<\/i><\/a>. <\/p>\n The terminology is weird and counter-intuitive thanks to the history of the registry. Back in the days before named values, you queried the data associated with (the default value of) a key by calling I’m sorry. <\/p>\n “Raymond, you idiot” section<\/b>: <\/p>\n “Sure, Raymond, that’s the historical reason why the terminology is messed up, but why hasn’t anybody fixed it in the meantime<\/a>?” <\/p>\n Well, changing terminology at this point would probably create even more confusion. For example, suppose you decide that the terminology should be changed as follows: <\/p>\n I agree with you that this terminology would probably be much less confusing, but how do you get there from here? When you update all the documentation to change the terminology, how do you know that you covered everything? Do you grep for the word key<\/i> everywhere and then decide on a case-by-case whether it should be changed to node<\/i>? That’s probably some hundreds of thousands of hits just inside the MSDN Library. (Even worse with value<\/i>, type<\/i>, and data<\/i>.) And then there are all the comments in source code that are now wrong. And all the magazine articles written prior to the change are now wrong; who’s going to go update them? And the existing source code needs to change Bonus chatter<\/b>: There’s also this thing called a class<\/i>. I have no idea what it’s for, so don’t ask. <\/p>\n","protected":false},"excerpt":{"rendered":" Hives, keys, values, types, and data. As I noted some years ago, the file that holds the registry data is called a hive. A hive contains a tree of keys. Keys contain a list of values. Associated with each value is a type and data. The terminology is weird and counter-intuitive thanks to the history […]<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[26],"class_list":["post-19263","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-other"],"acf":[],"blog_post_summary":" Hives, keys, values, types, and data. As I noted some years ago, the file that holds the registry data is called a hive. A hive contains a tree of keys. Keys contain a list of values. Associated with each value is a type and data. The terminology is weird and counter-intuitive thanks to the history […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/19263","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=19263"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/19263\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=19263"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=19263"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=19263"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}RegQueryValue<\/code>, which was a rather natural name since it matches the key\/value pattern. But the introduction of named values<\/i> threw this pattern into disarray. Perhaps a better name could have been chosen for what today are known as values and data, but what’s done is done and that’s the name we’re stuck with. <\/p>\n\n
\n Old<\/th>\n New<\/th>\n<\/tr>\n \n key<\/td>\n node<\/td>\n<\/tr>\n \n subkey<\/td>\n subnode<\/td>\n<\/tr>\n \n value<\/td>\n key<\/td>\n<\/tr>\n \n type<\/td>\n type<\/td>\n<\/tr>\n \n data<\/td>\n value<\/td>\n<\/tr>\n<\/table>\n HKEY<\/code> to HNODE<\/code> and RegOpenKey<\/code> to RegOpenNode<\/code>. Okay, so maybe you leave the old names around for compatibility, but now you have the problem that RegOpenKey<\/code> returns a node, not a key, and that you pass a key name to RegQueryValueEx<\/code>, and what the heck does RegDeleteKey<\/code> do? Does it delete an old-key or a new-key? <\/p>\n