You don't need static_cast (or any cast) to convert any pointer type to void.

#include <string>
int main(void)
{
	std::string *pString = new std::string;
	*pString = "Hello world!";
	void* pVoid = pString;
	delete pVoid;
}

Select allOpen in new window

thanks a lot for ur help n support
i have got my answer

>> i have used static_cast at many places in my code can it lead to memory leak if used in a improper way
Apart from casting void pointers to non-void pointers (and vice versa) static cast will not allow you to cast unrelated pointer types. For this you should be using reinterpret_cast. For down-casting (from a polymorphic super to a sub class) you would normally use dynamic_cast to confirm the super IS_A sub class relationship.

I'm sure you could contrive a way (if you really tried) to leak memory, but I can't think of a normal and reasonable use for static_cast that would do this.

What I'd be more worried about is that you need to use "static_cast at many places". The use of cast is rarely required if code is structured right. It's usage coerces the compiler into ignoring potential problems in your code and can shadow issues. Are you really sure all the times you've used cast you've really needed to? Are you sure you couldn't find a better way?

-Rx.

additional...

The one to take real care with is const_cast. If you use this to cast away constness on a type that was originally defined as const and then you try to modify it you'll almost certainly cause a  program crash. This is because data types declared const are frequently stored in read-only memory. It is; however, safe to cast away constness on a type that has acquired const (say, through the call stack) but wasn't originally defined as const. This is because the original type will live in read/write memory. Again; however, the need to use const_cast (except when interfacing to 3rd party APIs) is usually indicative of poor design -- your code isn't const correct.