>> Well I did say I hated to mention it (mostly for the >> reasons you oulined)... > > Sorry Jeremy. I hope I didn't come across as bashing > you personally, because I certainly didn't mean it > that way.
No worries, I didn't take it that way, I thought you were bashing VB programmers in general ;-) No, not really, I am just kidding :) It wasn't in my original email about the useful functions in the VB runtime that aren't part of the CLR, so it would have seemed you were doing a good, thing for guiding an errant soul back to the extra and better functionality the CLR provides :) Much like suggesting to someone who only used functions that classes might be nice :) Also I thought you were geting at an eminently sensible point of avoiding "code bloat" and "cpu burn", two common features of today's software (the third being, "memory haemorrhage" but maybe the GC will help with that one). I'm not sure if there is a design pattern for these paradigms but there should be, where does everybody learn it from? :) (Although, even I'm guilty of this usually when uncomfortably tight deadlines become involved) Sorry, if I came-off offended, but I think the chuckle in my throat doesn't always seem to come across in text ;) My MS.VB.Financial was to illustrate a point, though I don't really use it, and obsure it may have been (I just lifted the text from the object browser, I don't normally sound like a textbook). It is worth making people aware that the VB libraries are there for C# and they have functionality that is not available in the vanilla CLR, if they need that sort of thing. Which is a point you yourself hinted at so no complaints there. It may be in the MS.VB namespace, but that is irrelevant was may main point, but I recon 90% of C#, managed C++ users would not use those functions for that reason or would not even think of them and cook something up themselves from half remembered formulae. So unless there is a better way of doing in the CLR; as there is with the question asked, the C# equiv of the VB function is the VB function - as all languages are IL - just some more than others ;-) > You could always rip the IL too, but that could > end you up in court. ;) Yeah, and I'll probably get flamed for writing off topic, spuriously and at length, but these are the breaks :-) Take care of yourself, Jeremy You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
