Footnotes

1. This function also takes some parameters that provide contextual information to the binding process which we shall get to in a moment. [Back]

2. The reason behind this rule lies in the fact that in order to look in the Running Object Table, we need the whole moniker in its fully reduced form. If the current moniker is but a piece of a generic composite, then it has to be the composite's responsibility for doing the reduction; the moniker cannot do it correctly do it by itself. [Back]

3. In fact, the Win32 implementation of File Monikers does have this behavior. An alternative to the non-generic composition implementation described here is that the elements in a path are each separate monikers which are then generically composed together. [Back]

4. fOnlyIfNotGeneric is set by recursive ComposeWith() calls from the implementation of Generic Composite Moniker -ComposeWith(). [Back]

5. The definition of FILETIME was taken from the Microsoft Windows 32 specification. [Back]

6. Letters, numbers, or periods; must not begin with a number. See the appendix. [Back]

7. This function is a member of IMoniker interface rather than an independent API function in order that future revisions of this function can be correctly correlated with revisions to system moniker classes. [Back]