pid_t is supposed to be an "unsigned" data type not "signed" datatype, this is the same reason why you used %u for unsigned. so you need to correct this, else it will be misleading to beginners. Your videos are very good anyways, keep it up.
Hello, glad you pointed this out.. Actually from the man pages.. It says pid_t is a SIGNED integer data type; then "why use a %u would be natural follow up question". The thing is a lot of people use %u because the pid returned by getpid is always positive (In Unix like operating systems). Please go ahead and verify it and let me know what you see. Always open to learn and be corrected. Cheers..
@@jess-inspired i guess you’re right, normally _t represents an unsigned integer (32 bit), but in this case they’re making the program portable across platforms, regardless of whether, e.g., a PID is 16 or 32 bits or 64 bit, therefore making it signed. This makes sense. Thank you. 🙏
In addition, another reason the pid_t is signed is so you'll be able to handle the -1 return value if the system call fails. (That is for system calls that actually can fail, getppid and getpid are exempted in this case (they are always successful))
Brother I got to give it to you.🙌🙌🙌🙌. You teach way better than any other person Ive listened to so far. I was giving up on this thing Until I came across your tuitorials. ALX should hire you
Without good creators like you. We that mostly learn best by watch videos than read will not survive. Thanks a lot for your detailed content and explanation.
Currently watching and honestly most of all the things I read are beginning to make sense. I might actually become a software engineer after all 😅. Thank you!!!
I must comment that you are the best ALX instructor i have come across, you have helped me a lot for the shell project ALX. if I had a mean I can subscribe to your channel 1 million times. Thanks you so much, please do more videos on the printf project. GOD bless you bro, your place dey. #ALXcohort9
Thanks a lot, bro. I'm doing the project during break0 because I had midterm exams, and this is quite helpful. I would be so grateful if you could make videos on printf project.
Thanks Jess. Your tutorials are short, clear and precise. Is pid_t data type signed or unsigned? You wrote 'signed' in the explanation but you used unsigned in your format specifier .
Thanks a lot. Great observation. A viewer asked this question some time ago too in the comments; just pinned our conversation where I explained it. Feel free to check it out.. Cheers
Not sure about this, haven't looked at standard libraries.. I know it's defined in the sys/types.h header file and the unistd.h.. Including any of those header files gives you access to pid_t
Наука
pid_t is supposed to be an "unsigned" data type not "signed" datatype, this is the same reason why you used %u for unsigned. so you need to correct this, else it will be misleading to beginners. Your videos are very good anyways, keep it up.
Hello, glad you pointed this out.. Actually from the man pages.. It says pid_t is a SIGNED integer data type; then "why use a %u would be natural follow up question". The thing is a lot of people use %u because the pid returned by getpid is always positive (In Unix like operating systems).
Please go ahead and verify it and let me know what you see. Always open to learn and be corrected. Cheers..
@@jess-inspired i guess you’re right, normally _t represents an unsigned integer (32 bit), but in this case they’re making the program portable across platforms, regardless of whether, e.g., a PID is 16 or 32 bits or 64 bit, therefore making it signed. This makes sense. Thank you. 🙏
@@josephjohn4810 Thank you all for this discussion, actually learnt more😁
In addition, another reason the pid_t is signed is so you'll be able to handle the -1 return value if the system call fails. (That is for system calls that actually can fail, getppid and getpid are exempted in this case (they are always successful))
Very much simplified!... thank you Jesse!!!
Amazing video Jessi. You are great at simplifying SE concepts. Good job and looking forward to the next video
Your video is indeed inspiring as you take your time to explain the concepts with clarity. I can't wait to watch the upcoming videos!
Thanks Jesse, this is amazing.
very clear illustrations. more videos please.
Keep the videos coming please, this is really good.
You just simplified the pid to my understanding, thanks....
Thanks jesse this so clear God bless you
The clarity is 💯
Great work Jesse 👍
Nice one Jesse 👍
Brother I got to give it to you.🙌🙌🙌🙌.
You teach way better than any other person Ive listened to so far.
I was giving up on this thing Until I came across your tuitorials.
ALX should hire you
Wow. Everything is beginning to make sense about this shell thing. Thank you so much
It's an honour to be of help
Clear explanation.!
Good explanation. Keep it up
Jessi, you're amazing, Thanks so much for this. Thank you so much. You're great.
You're welcome bro.. Glad it helped
Nice thanks a lot man
Without good creators like you.
We that mostly learn best by watch videos than read will not survive.
Thanks a lot for your detailed content and explanation.
Most appreciated🙏🏾
Thank you
Currently watching and honestly most of all the things I read are beginning to make sense. I might actually become a software engineer after all 😅. Thank you!!!
Glad they're making sense. You sure have all it takes to become an SE, and a great one at that. You're welcome
Great audio and great content. simple and short.. thank you
You're very much welcome
for my cute minishell~!!
I must comment that you are the best ALX instructor i have come across, you have helped me a lot for the shell project ALX. if I had a mean I can subscribe to your channel 1 million times. Thanks you so much, please do more videos on the printf project. GOD bless you bro, your place dey. #ALXcohort9
Thanks man. Really really appreciate..
God bless you sir,what a wonderful explanation 👍... Keep it up it is helpful
You're very much welcome. Glad to be of service..
nice
so nice bro . thanks
You're very much welcome
Thanks a lot, bro. I'm doing the project during break0 because I had midterm exams, and this is quite helpful.
I would be so grateful if you could make videos on printf project.
Youre welcome.. Glad its helpful. Yeah, really considered the printf.. Let's see how it goes.
Good Stuff... Concise to say the least...
Thanks a lot..💯
🥂
Nice video sir.
I also want to ask: Why did you use the format specifier %u to print the PID since you mentioned that it is a signed integer?
Thanks Jess. Your tutorials are short, clear and precise. Is pid_t data type signed or unsigned? You wrote 'signed' in the explanation but you used unsigned in your format specifier .
Thanks a lot. Great observation. A viewer asked this question some time ago too in the comments; just pinned our conversation where I explained it. Feel free to check it out.. Cheers
I don't know to get Man Page. Please help me.
the pid_t was it defined using a typedef??
Not sure about this, haven't looked at standard libraries.. I know it's defined in the sys/types.h header file and the unistd.h.. Including any of those header files gives you access to pid_t
@@jess-inspired thanks Jesse, i will check those libraries and give you feedback
for those--->> this series is not completed yet.... and you wont be getting your own shell even after completing this 10 videos :(
Pls do I have a whatsaap or telegram platform?
t.me/alxsupportgroup
Hello Amarachi..
Not my group though but you can find me here..
Cheers..
Hello boss plz how can I contact you