How to create in memory QFile

[sonulohani]

Who said that QFile should always be on stack? Its depend on you whether you want to allocate in stack or heap.

[ChrisW67]

QBuffer is the in-memory QIODevice you might want.

[amleto]

Who said that QFile should always be on stack? Its depend on you whether you want to allocate in stack or heap.

nobody said that.

If, however, you are going to write an example that looks like a java programmer wrote it, perhaps you should expect some comeback.

[sonulohani]

Then do coding in java, why r u here? Its depend on your program methodology. And if someone is here than atleast he should know the basic concept of c++(memory allocation). You shouldnt have to think about what they do with this code or if he /she will understand this code or not. Okay, point out the line that is causing memory leak in my code.

[spirit]

Okay, point out the line that is causing memory leak in my code.

...
if (!file->open(QIODevice::WriteOnly | QIODevice::Text))
         return; //memoy leak if a file can't be opened
...

...
if (!file->open(QIODevice::WriteOnly | QIODevice::Text))
         return; //memoy leak if a file can't be opened
...

To copy to clipboard, switch view to plain text mode 

The simplest way to fix this without using delete it's just provide a parent in QFile's ctor.

[amleto]

No, simplest way is to say `QFile file;`, not `QFile* file = new ...`

[spirit]

No, simplest way is to say `QFile file;`, not `QFile* file = new ...`

Yup, and change all "->" to "." if you have tons of code.

[amleto]

Then do coding in java, why r u here? Its depend on your program methodology. And if someone is here than atleast he should know the basic concept of c++(memory allocation). You shouldnt have to think about what they do with this code or if he /she will understand this code or not. Okay, point out the line that is causing memory leak in my code.

You are the one writing like java: Allocating on the heap when only a local variable is needed - check. Using new without delete - check.

Your leak has been pointed out already, although why you couldn't see it for yourself is concerning.