C++ : stream ^ | v C++ Library : file descriptor ^ | userspace (process) ---+++--- | kernel space (system) v OS : inode

I don't understand the linking of streams and libraries. So, these are a bit difficult for me to understand.

C++ : stream ^ | v C++ Library : file descriptor ^ | userspace (process) ---+++--- | kernel space (system) v OS : inode

I am imagining stream as a channel between the CPP program and the monitor

can I consider a .txt or a .bin file (just supposing that I am reading from .txt or .bin file) as a File

C++ : stream ^ | v C++ Library : file descriptor ^ | userspace (process) ---+++--- | kernel space (system) v OS : inode So where is File in the above representation?

Can you explain the above diagram yourself?

It's mostly not about C++ but about operating systems which is off-topic for this chat

I personally think it is required for him to understand how the language works on the inside to get what a file and a stream are

I don't think that these details matter on his level of knowledge

Well he looks like he have the basics on CS but no idea on the practical way things work

I tried two different cases provided in this link to understand the concept of buffers in C++ Yet both work the same on my 32-bit code blocks IDE. https://www.google.com/amp/s/www.geeksforgeeks.org/buffer-flush-means-c/amp/ Please suggest corrections.

But i can't really understand until my experiment results out the same. I do not mean to offend but you need to see things to believe them.

Well he looks like he have the basics on CS but no idea on the practical way things work

I would love to learn the internal implementation detail. Any online resource or course on operating system?

Anyone suggest me how to use chrono library

run-time based only. when you use virtual , your class go to the vtable to check for the respective object's function

12345 this is a number and I get this number forms of different 5! Types.get the numbers by program

Why isn't there any concept of virtual constructor in C++?

I didn't know about virtual destructors too. Well, this is another question why is there any virtual destructor concept in CPP?

I know that if the base class pointer points to the derived class base *b = new Derived(); and if we do delete b; then only the destructor of base class runs and not that of the child class. That's why we need to make the base class destructor virtual for the child one to run.

I just know that it doesn't run.

first: destructor for derived class second: destructor for basic class

man, try it on practice...

I know that if the base class pointer points to the derived class base *b = new Derived(); and if we do delete b; then only the destructor of base class runs and not that of the child class. That's why we need to make the base class destructor virtual for the child one to run.

Because unless you declare your function as virtual, it uses early binding / lookup and does not know abouthe any child instance

I know that if the base class pointer points to the derived class base *b = new Derived(); and if we do delete b; then only the destructor of base class runs and not that of the child class. That's why we need to make the base class destructor virtual for the child one to run.

Tell me about what happens just after we write delete b;

Tell me about what happens just after we write delete b;

call child destructor, then basic destructor

I guess someone can brief it in a few lines. Although I am gonna surely read it later.

If Base class destuctor is not virtual then only Base class destructor is called

If Base class destuctor is not virtual then only Base class destructor is called

Try it please

I thought if we have situation like this, basic destructor should be as virtual