Returned to my own naming convention - at the latest, the 'SingleInt32Union' would raise the question about where there is only a single int32 in that union
git-svn-id: file:///srv/devel/repo-conversion/nusu@295 d2e56fa2-650e-0410-a79f-9358c0239efd
This commit is contained in:
parent
5fb5b1f568
commit
2210973528
2 changed files with 17 additions and 17 deletions
|
@ -36,8 +36,8 @@ namespace Nuclex.Support.Collections {
|
|||
/// </para>
|
||||
/// <para>
|
||||
/// In principle, it works like a multimap, associating keys with a number of values
|
||||
/// and allowing you to look up a values by their keys. Unlike a multimap, it will
|
||||
/// avoid handing out a previously provided value again.
|
||||
/// and allowing you to look up values by their keys. Unlike a multimap, it will try
|
||||
/// to avoid handing out a previously provided value again as long as possible.
|
||||
/// </para>
|
||||
/// <para>
|
||||
/// A typical usage would be to set up a mapping between situations and dialogue lines.
|
||||
|
@ -282,6 +282,6 @@ namespace Nuclex.Support.Collections {
|
|||
|
||||
}
|
||||
|
||||
} // namespace Nuclex { namespace Support { namespace Collections
|
||||
} // namespace Nuclex.Support.Collections
|
||||
|
||||
#endif // !(WINDOWS_PHONE || XBOX360)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue