Read All File Lines Into A Dynamically Allocated Array Of Strings | C Programming Example

[@Majkieboy]

Very happy to have found these, not enough C content around these days. Good job.

[@PortfolioCourses]

Thank you, I'm glad you found the channel too! :-)

[@MrBolcetik]

I am currently an active student in Software Engineering, and every time you post a video it always related with the content that I am currently dealing with 😂. Thank you for this great video!

[@PortfolioCourses]

You're very welcome! :-) And I'm really glad to hear these videos are relevant to what you are learning as a student... helping students is the biggest reason why I like making these videos.

[@MrBolcetik]

@@PortfolioCourses I was coding a function called get_next_line and this is just what i was needed 😊

[@fifaham]

Very helpful and useful, thank you Kevin. The good things about microcontrollers is that they can have their built-in memory expanded by connecting them to external memory, and that can be very large. A multiple blocks of memory chips can store large files of data and text for processing them at later time.

[@PortfolioCourses]

You're welcome Firas! :-) And thank you for sharing this information with everyone too.

[@edenng8431]

Fantastic! Great details! Thank you for updating the C series.👍

[@PortfolioCourses]

You're welcome Eden, I'm glad you enjoyed it! :-)

[@arthur_p_dent4282]

Your content is second to non. Thanks you so much.

[@PortfolioCourses]

You’re very welcome Arthur, and thank you for this kind feedback! :-)

[@dev_ression]

great explanation bro!

[@PortfolioCourses]

Thank you for the positive feedback, I’m glad you enjoyed the explanation! :-)

[@dev_ression]

@@PortfolioCourses no problem!

[@naboulsikhalid7763]

Great content, I think everything is mentioned here. Thank you KEVIN

[@richarddaygm]

It is obvious but worth pointing out sizeof(char) is always 1, unlike sizeof(char *) which is the size of the pointer. So in the realloc, there is no point in timesing by sizeof(char), even though it would be more symmetrically pleasing!

[@idanmariani8601]

thank you very much like allways.. i wish everyone will get to know your awsome channel and have tons of subscribed your the best teacher ever.. :)

[@PortfolioCourses]

Thank you very much for the support Idan! :-)

[@bettyswunghole3310]

"Stack Overflow" strongly recommends *_against_* using statements like "if (feof(file))" for reasons I didn't fully understand...

[@sgarcia1070]

I have two quick questions, what is the purpose of using the value of 1024 as suppose to another value, and my second question is does free() erase what’s in the string?

[@PortfolioCourses]

There is no particular reason. It's a big round number that's divisible by 2 (divisibility by 2 can 'play well' with computers in general, compared to something like 537 or something). Another strategy we could use that may be better in some circumstances is to double the amount of memory allocated for the block each time. I've taken an assumption that this would be overkill and that more conservatively increasing the size by 1024 will be OK. And no, free() does not erase what's free'd. Those are both great questions by the way! :-)

[@dogdog5994]

A little suggestion. You made a video about threading in C using the POSIX pthread library. I suggest videos about C11 threads and maybe more videos about POSIX threads (pthread).

[@PortfolioCourses]

It’s funny you’re reading my mind haha, I’ve thought of doing more posix thread topics related to things like mutexes, passing arguments to functions, etc. And C11 threads is a topic I want to cover for sure too! :-)

[@dogdog5994]

POSIX pthread vs. C11 threads and the differences would be an interesting topic too. Various compilers have supported pthread for quite a long time but it's not a part of the official C Standards. There was no official threads in the C Standard until C11 as far as I know.

[@PortfolioCourses]

My understanding is that "underneath" C11 threads are implemented as pthreads in most platforms that support pthreads, and that pthreads are more widely used due to supporting more features even though C11 threads are more portable.

[@yamithere_]

I just wanna ask what is the difference between having brackets after the for loop and nesting the next for loop compared to the ones without the brackets?

[@PortfolioCourses]

When we use brackets, we an have multiple statements in the "body" of the for loop. Without brackets, we can only have a single statement. :-)

[@yamithere_]

@@PortfolioCourses Thank you!

[@PortfolioCourses]

You're welcome! :-)

[@ziwaang2250]

Great video! For a 2D string array, would it then be "char ***" ?

[@PortfolioCourses]

Yes, that should work, and what you would have would be a 2D array of pointers to strings essentially. :-)

[@ziwaang2250]

@@PortfolioCourses Thank You!

[@pragunmike1642]

This is fab. Thank you 🙌🏻🙌🏻🙌🏻

[@PortfolioCourses]

You’re welcome, I’m glad you enjoyed it! :-)

[@LMZ914]

Thank you sir you are the best

[@studentofedison421]

why **line instead of *line . why line is a pointer to pointer to char instead of pointer to char

[@Mo3au4HbIu_Ba3oH]

I was looking for some copper, but found the real gold

[@PortfolioCourses]

I’m glad you enjoyed it! :-)

[@ramakrishna4092]

Wonderful explanation sir and congratulations for 22k sub...👏👏👏 I have doubt here .. typedef int (*function)(int a, int b); this is one way I know typedef the function pointer but I'm getting confused how this is acting as function pointer Below syntax can you pls explain this . "typedef int function(int a, int b);" I have also found this code sample using the above syntax #include int add(int a, int b) { return a + b; } int sub(int a, int b) { return a - b; } typedef int function(int a, int b); int call_function(function *p, int a, int b) { return p(a, b); } int main(void) { int sum; sum = call_function(&add, 10, 5); printf("add: %d ", sum); sum = call_function(&sub, 10, 5); printf("sub: %d ", sum); return 0; }

[@PortfolioCourses]

Hi Rama, it looks like this line here: typedef int function(int a, int b); is creating "function" as a typedef, effectively a synonym, for a function that returns an int and accepts two ints as arguments. And then here: int call_function(function *p, int a, int b) { call_function accepts a pointer to a function like this as an argument, which is supplied when it is passed the address of add and sum. :-)

[@jerryli5555]

The getline() Function can read a whole line

[@IanHouchin]

So does fgets. But getline() is a bit more complicated than fgets.

[@yoruichi5802]

I tought it was forbiden to exit a loop with a break

[@PortfolioCourses]

No, it’s not forbidden, it’s part of why it’s in the language. :-) Maybe a teacher would advise a student not to use break so students learn to use loops “the normal way”. But using breaks in a loop is normal in practice.

[@yoruichi5802]

@@PortfolioCourses true!

[@PortfolioCourses]

@@yoruichi5802 🙂

[@YoungOrbital]

while( !feof(file) )