Question 1

Does every part of your vector struct get used? I'm going to make my own as more C practice/preparation before continuin...

Accepted Answer

Hello,
Not everything gets used but you dont need to write anything anyway, its a quick copy and paste if you watch from the start of the course youll find it, I show you where to find the vector files. We dont implement that functionality ourselves as its not related to compiler dev

Thanks

Question 2

Hi Daniel - I've just completed coding up to Lesson 98 & things are working using test.c from the video. However I get a...

Accepted Answer

HI congratulations on getting to Lecture 98 so far. I have tested the code on the main repository in its current final state and can confirm that it also crashes with a segmentation fault. This means theres a bug in our project so I will create a lecture in due time where we fix this problem.

Module 3 is due for release 1st of January 2023. I will ensure theirs a bug fix for this in that module. Module 3 will of course be apart of this course series as you have purchased the right for all future modules to be included

Glad your enjoying the course

Thanks

Question 3

Hi Daniel - It appears that the video for Lesson 105 "Building the fundamentals" has been cut short - It's only 1m17s ?...

Accepted Answer

Hi Tim,
This problem has now been corrected, sorry about that our employee must have uploaded an unedited clip or some sort of error occured during the upload. The correct video file in its full duration has now been uploaded. As for the commit logs being different from the lesson numbers this is because at one point I back tracked and made a lecture before another one. As you know git history is permenant. That is why the lesson numbers do not match up but they are pointing to the correct source code. Better to focus on the commit titles going forward than the lesson numbers attached to them.

Thanks

Question 4

Hi Daniel - I'm just going over some stuff & wonder if you could please give me recap of the uses & differences between...

Accepted Answer

Hi Tim,
Yes sure, node_tree_vec is the root of our tree, so you can imagine C functions being in here, C global variables and so on. What it wont contain are things like if statements because if statements have a parent node right. Anything that cant have a parent node you can expect to end up in the node_tree_vec.

node_vec is used during the parsing process as a way to push and pop things, so if we find 50 we push to the node_vec we find + we push to the node vec, we find 20 we push to the node vec. Pop it all off and then create an expression node then push that back to the node_vec. So that is what the node_vec is used for, to assist during the parsing operation. When parsing is done we iterate through the node_tree_vec which contains everything we care about.

Question 5

Hi Daniel,
First of all,. Thank you for making this course. This will greatly help me understand computer science (comp...

Accepted Answer

Hi good question. Originally module 3 was due for release 1st of December however I moved country which means I have been very busy lately. I moved back home to UK. I then ended up with covid so their has been some unfortunate delays

The new release date for Module 3 is 1st of January.  Though I can't make promises that this date everything will be done we are pretty close . If I find the delay will be longer by more than a few weeks into January I will upload all of module 3 that is ready and continue to add videos daily until module 3 is entirely uploaded 

Please keep an eye on the course description as I will be sure to update it when theirs changes 

Thanks
Dan

Question 6

I understand that we have a temporary stack of nodes that we push/pop as we build the tree, but for some reason I'm stru...

Accepted Answer

Hi, usually you use grammer parsers so you use a special grammer syntax and pass it into a parser which follows that grammer as rules. You can read more about that here: https://www.geeksforgeeks.org/types-of-parsers-in-compiler-design/

For more complicated parsers it is sometimes best to avoid grammer parsers that take that rule input. Our parser in this course for example is completley programatic, we use no grammer at all we manually parse every part of the C language.

This allows us to have more flexibility of how we parse and making changes can be easier. I'm unable to give a name to this type of parser because it does not use a grammer. We manually parse everything. Theres probably a name for the type of parser it is but it is not so important.

Well take an input of 50 + 30 . This in our compiler results in an expression node that holds a left node and a right node. Left being 50, and right being 30. 

What is it that your struggling to understand so I can help more.

Course Questions

Questions

Does every part of your vector struct get used? I'm going to make my own as more C practice/preparation before continuing on with...

Hi Daniel - I've just completed coding up to Lesson 98 & things are working using test.c from the video. However I get a segmentat...

Hi Daniel - It appears that the video for Lesson 105 "Building the fundamentals" has been cut short - It's only 1m17s ? And a very...

Hi Daniel - I'm just going over some stuff & wonder if you could please give me recap of the uses & differences between the compil...

Hi Daniel, First of all,. Thank you for making this course. This will greatly help me understand computer science (compiler desig...

I understand that we have a temporary stack of nodes that we push/pop as we build the tree, but for some reason I'm struggling to...