I am beginner at C++, I came to it from java. Java learning is never a bad idea but I am enchanted to C++ by its speed and flexibility in coding world which ironically most of new programmer hates XD. But really great job at explaining the videos, really great explanations and simple. Keep the great job legend and I hope to see more of your videos related to C++.
@1:53 and @4:44, it is actually not waiting for that lock , it will throw the run-time error if the same thread is trying to lock itself the second time.
Thank you Sir! I am giving interviews with the help of your videos only. One suggestion, just for visual better presentation. The comments section in your videos, the text colour is very light. Those points are very important, and while watching loose focus or interest on those points. Could you please change the colour of the comments section, to brighter colour? Thank you for all the valuable contents. Regards.
Concept wise i understood but i have a question. Why to go for recursive mutex. It can be done by simple mutex .Just we need to take care that only one thread should be accessing the critical section and it can be done by keeping the function call in mutex. Means instead of keeping mutex inside the function why not keep mutex lock from where the fucntion is getting called? If I am missing some point where it can fail,Please let me know.
Hi I got concept of this...thank you very much....I have a doubt in example.. first coding example illustrates recursive lock... If recursive call is made from function , it could have been made post we do unlock.... i.e. do unlock first and then call recursive call.. does this not work...? General question is that assume recursive function has critical section but who or which limits us to unlock mutex before self calling?
I am beginner at C++, I came to it from java. Java learning is never a bad idea but I am enchanted to C++ by its speed and flexibility in coding world which ironically most of new programmer hates XD.
But really great job at explaining the videos, really great explanations and simple. Keep the great job legend and I hope to see more of your videos related to C++.
you gonna love GoLang, it has more flexibility of writing codes and its much more efficient than java.
You doing a great job! Keep going :)
Sure man!!
Thanks for the comment!!
@1:53 and @4:44, it is actually not waiting for that lock , it will throw the run-time error if the same thread is trying to lock itself the second time.
Extremely helpful that opens my mind a lot. Tks!!!
Glad to hear it!
pratical impelementation in last would be cherry on cake!
Thank you Sir! I am giving interviews with the help of your videos only.
One suggestion, just for visual better presentation. The comments section in your videos, the text colour is very light. Those points are very important, and while watching loose focus or interest on those points. Could you please change the colour of the comments section, to brighter colour? Thank you for all the valuable contents. Regards.
@12:34 I'd place the code at line 38 inside the lock after line 36. Otherwise, it will cause some messy outputs on some random executions!
Your thread seriese is awesome. :)
Thanks man..
The code:
// Example 1: With recursion
#include
#include
#include
using namespace std;
std::recursive_mutex m1;
int buffer = 0;
void recursion(char c, int loopFor){
if(loopFor < 0){
return;
}
m1.lock();
cout
Nice explanation Sir,
we are waiting for your videos on c++
Thanks for the comment dude!!
Sure there are so many videos coming on c++.
Great explanation.Thank u
Thanks for the comment dude!
Concept wise i understood but i have a question.
Why to go for recursive mutex.
It can be done by simple mutex .Just we need to take care that only one thread should be accessing the critical section and it can be done by keeping the function call in mutex.
Means instead of keeping mutex inside the function why not keep mutex lock from where the fucntion is getting called?
If I am missing some point where it can fail,Please let me know.
because the lock will not let the same thread to acquire lock again. results in deadlock
Hi I got concept of this...thank you very much....I have a doubt in example.. first coding example illustrates recursive lock... If recursive call is made from function , it could have been made post we do unlock.... i.e. do unlock first and then call recursive call.. does this not work...? General question is that assume recursive function has critical section but who or which limits us to unlock mutex before self calling?
the video helped me a lot
Glad it helped!!
Hi may I please know which software do you use to draw using that sketch style drawings ? You explain really well !
Please add videos for c++11 features, lamda function, for each etc..
Sure man now i am in mood to complete these 11/14/17/20 list.
if you can put the code in your blog, it would be very helpful for us. Thanks for your videos.
I was afraid when the warning suddenly appeared😄
:D :D
There is something called recursive_timed_mutex.
Can you give a video on it.
excelent
Thanks..
Nice work :) , please upload threading playlist code file on git hub
Thanks @Anshu..
You can become a small member of my channel, then you can get code for any video. (It's very cheap)
TH-cam lacked you.