http://msdn.microsoft.com/en-us/library/windows/desktop/ms724897%28v=vs.85%29.aspx
ulOptions
This parameter is reserved and must be zero.
What was the reason behind placing this formal parameter, whereas it always must be the same value?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The official Microsoft docs don’t say anything but the wine code does:
RegKeyOpenEx()accepts theREG_OPTION_OPEN_LINKvalue tooptions, which in the case of registry keys that are links, opens the link itself rather than following the link and opening the target.However since it’s not in the official docs, I don’t recommend using it. Since Micrsoft don’t mention it, they don’t officially support it, and are free (within practical limits) to stop that working in a windows update or whatever.
Microsoft are free to add whatever parameters they like to their functions simply to have a parameter to make use of later on. It can save them having to create new functions (although they don’t seem to have done too well in that regard anyway).