If you want to, then go ahead. However, if you're working in the.net environment the last thing you probably want to do is C++ - last I looked, the Microsoft additions to C++ for.net were disgusting.
I believe the "using" the poster was talking about was the C# keyword that provides automatic.Dispose() execution once the block is out of scope. It's a shortcut for wrapping the code in a try-finally and calling Dispose() in the finally.
For example if SomeClass implemented IDisposable:
using (SomeClass x = new SomeClass()) {// work }
would be equivalent to
SomeClass x = new SomeClass(); try {// work } finally {
x.Dispose(); }
If you want to, then go ahead. However, if you're working in the .net environment the last thing you probably want to do is C++ - last I looked, the Microsoft additions to C++ for .net were disgusting.
I believe the "using" the poster was talking about was the C# keyword that provides automatic .Dispose() execution once the block is out of scope. It's a shortcut for wrapping the code in a try-finally and calling Dispose() in the finally.
// work
// work
For example if SomeClass implemented IDisposable:
using (SomeClass x = new SomeClass())
{
}
would be equivalent to
SomeClass x = new SomeClass();
try
{
}
finally
{
x.Dispose();
}
A local newspaper's website started getting popups through firefox sometime during the last couple months. http://www.sj-r.com/