From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2006-09-08 11:14:46
Phillip Seaver wrote:
> Rene Rivera wrote:
>> How are those different from the existing "W32_GETREG" builtin?
>> See the bottom of
> Looks to me like the W32_GETREG builtin just lets you get one value,
> while those let you enumerate values and keys.
>> Bojan Resnik wrote:
>>> Sometimes, especially when needing to detect installed versions of
>>> some third-party program, I need functions to enumerate registry
>>> subkeys or registry values of a given key. I have written two new
>>> builtin functions W32_REGKEYS and W32_REGVALUES which, given a
>>> registry key path, return lists of its subkeys and values,
>>> for local subkey in [ W32_REGKEYS "HKLM\\Software\\Microsoft" ]
>>> ECHO $(subkey) ;
Could this one be done by modifying the existing W32_GETREG to return
subkeys? ... Hm, I guess that wouldn't since registry entries always
have a value.
>>> for local value in [ W32_REGVALUES "HKCU\\Environment" ]
>>> ECHO $(value) ;
Maybe it's this particular example, but that one seems problematic. Does
it return the "Data" part, the "Name" part, or both?
I'd think that both of the above could be covered by just adding a
single new rule W32_GETREG_KEYS to return the names and subkeys of the
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk