Two way communication between processes (using pipes) in C

[canaljuunin]

I'm amazed by this power you have to explain complex stuff like this in such short videos. I've watched almost every single one of them. thanks!

[JYSERroshanseeam]

you are the best! you taught me this better than my university prof

[psebevx]

I like the return statements in the same line, makes it cleaner and easier to follow. Ty for the great videos.

[hectordoyle]

1. Great video
2. In response to your question: returning different values is convenient, easy to debug and understand, so for video purposes it may be a good idea to keep it as it is.
But speaking of error handling - plain return statement may be not the best choice for more complex applications. So if I may, I'd like to suggest creating a video about error handling alternative approaches. We know that C does not support exceptions that we know form Java and C++, so it would be nice to have something instead.
All the best!

[abhishekhm]

I am so lucky to have found this channel. Just amazing!!

[muhammedozen]

Awesome video. He explains a lot of stuff in as short as 10-20 mins. Great job. We're looking to see more content from you

[abugslife]

THANK YOU SO MUCH! You are helping me get through my operating systems class haha This has helped a lot :)

[grifo_-cyan]

Thank you so much! Your C language videos are saving me in my university courses.

[abdullahshahid]

You look like the nerd of the class.
Amazingly explained. love ya

[diego]

Im impressed, amazing job, finally i understand how pipes work.

[hunterkauffman]

About the same line brackets, my thinking is if the code can be read like a sentence left to right I'll make it one line.

I always summarize the functionality of inner code blocks when ingesting code, and whenever a code blocks a one liner I can save myself the effort in trying to remember what that code block does and interpret it literally instead of trying to remember what the summary of the high level functionality is

[ash_engineering]

Please make videos on Pthreads. Your teaching is very nice.

[ajayvembu]

You are doing an awesome job. Keep going & post more videos of such!! :)

[hingsing]

Great video! I wish that during the parts where the terminal result is not relevant, you would close it so we can see more of the code (helps process what is going on overall better). Or zoom out a bit so we can see more lines of code at once.

[poincareelcartografo]

On freeBSD it seems to always work fine with a single pipe.
Regarding your question, I have made a function in another file with its header.
You enter what read(), write(), etc... returns and the name of the function that generated it and prints out the error and executes the exit if it is -1 or, otherwise, prints out that the function has been executed. successfully executed.

[masoudsultanian]

Great explanation, Thank you
this is a good example of producer consumer problem with 2 processes with pipe() . could you please create a video explaining Multiple process producers and multiple process consumers using pipe()?

[liviuq]

Imho, it s clear and easy to follow your return values for the syscalls. I prefer using a macro to check the return value for syscalls because i like to also print why did the call failed.

[riper]

this really helped me understand this concept, thank you very much!

[HemekSC]

Hey, great video, i'm viewing this to repeat pipes for my univeristy exam, so, about bidirectional communication, i think that another reason becouse it work (with 2 pipes), is becouse the read syscall is a blocking operation, so if there isn't nothing to read the process wait unitil something is writted, is true?
Thanks a lot, you earn a new subscriber!

[jeremyberry]

I really hope you continue to make content!