>>>>>>Right, exactly. You just have to mark the code unsafe, so you would be doing this on your own risk.
>>>>>
>>>>>I would mark the code as "crap", I never understood the need of pointers in OOP, there should not even be mentioned :)
>>>>
>>>>:) They actually have their usage according to the book I referred to create quick stack based arrays...
>>>
>>>
>>>If you have to circumvent the language and its best practices, then there is something wrong with your design.
>>
>>That's a pretty narrow view. If you can gain a real, tangible benefit from circumventing "best practices", then chances are those "best practices" need to be revisited. That's how they evolve, and even how they arose in the first place.
>>
>>As for circumventing a language, that's how a language evolves, and it's a major driver in the development of new languages.
>
>
>Let me clarify my statement if you missed what I meant. If you need unsafe code in a managed program there is something inherently wrong with either your program design or you choice of the language to implement it.

I thought you were speaking more generally. Fair enough.