Much to benryves' chagrin, I've yet to give up on attempting to make Text my own little collection instead of using LinkedList<> or StringCollection. This iteration of 'design' is somewhat better than the last IMHO.



For review of what my previous one looked like:


No freakin' idea what I was thinking. Apparently to insert or remove a node, you had to make a new one at the specified spot. Like singletonesque nodes or something... [headshake] Washu is going to kill me.

Anyway, now I should just have to implement System.Collections.IList in it and it *should* be good to go. The only problem I've met so far is the some of the methods receive arguements of the type object. I scanned through the available exceptions for something akin to TypeNotSupportedException, but didn't find any. I went ahead and made up my own, but if there is a standard procedure for handling something like this, I'd be grateful if someone could leave it in a comment or message me. Thanks.

Edit: Or, in freaking retrospect, I could just implement IList and IList instead. :/

public class MyCustomCollection<T> : ICollection<T> {

    private LinkedList<T> Storage;

    public void Add(T item) {
        this.Storage.Add(item);
        // ... custom linking magic ...
    }

    public bool Remove(T item) {
        bool Removed = this.Storage.Remove(item);
        if (Removed) {
            // ... custom unlinking magic ...
        }
        return Removed;
    }

    public IEnumerator<T> GetEnumerator() { return this.Storage.GetEnumerator(); }

    // ... and so on and so forth ...

}