Comments by rj45 (Top 15 by date)

but I did approve it, I hope it does work :)

It would be pretty slow alternative in terms of performance.

hah nice!

Well usually I have an override that doesn't have that parameter but usually you need it. StringReader might be interesting, or some kind of iterator that acts like a cursor in the file.

returning null, isn't needed on errors because the lastMatch parameter returns -1. Although in some versions I had it returning null, I found this to be easier I think.

thanks this must be old code, I will find my latest version and submit tomorrow.

Your solution is cool but its not many times when your iterating through the same things.

what about this situation
getbetween ( a,b, 0, out last );
getbetween ( c,d,last, last;

I use that all the time.

Reason for my vote of 4
pretty cool

Marcus, Singleton means single instance and nothing more. In asp.net we multiple scopes of singletons ( not just static ). You may be expecting simply static, which would be single instance server wide, however in asp.net that is rarely what we want. My example gives us a single instance per session which is a singleton of the session context. If you want it per Request then you could use HttpContext.Current.Items.add rather than session which is a singleton of the request scope.



As you know, If you want it accessible from throughout the application make the property public static.

Reason for my vote of 2
a silly idea.

Did you get a chance to try it, I'd appreciate it if you could change your vote. ( if codeproject lets you do that..)

I suggest you try it out. I hint may be that it wouldn't work with foreach.

New fangled in regards to not needed recursion, yield, Ienumerable/foreach, Linq, templates. These things are not crap by themselves of course nor new things. They are simply not great IMHO for this simple context. I always laugh when I see the use of things to eliminate a loop or two thats why I posted this.