Write a 1 - 2 paragraph journal post, of at least 250 words, of what you learned this week in CST 334.
Man, where do I even start with this. Before I even begin talking about the C language itself (which I have never touched until this week), I want to state that I spent quite a while conceptually learning how Docker works. Apparently a docker image is just a fancy way of saying "here's a large folder that just contains the software code with all of its relevant files needed to run it (e.g. the correct java version, etc.)." A docker container is just a fancy word for "and here's a mini virtual environment that serves as a single instance of the image being run."
I then had to learn how to feel comfortable using a command terminal (Windows PowerShell) and be familiar with its relevant script lines/commands.
Then I began to learn the basics of C, including struct, pointers, and its relevant memory shenanigans. In particular, I had a hard time fully understanding pointers. But now I understand that (as I wrote in the first discussion week):
"a pointer variable stores the memory address of the original variable it points to. Therefore, as an example, the pointer variable named ptr that points to the original variable called var will contain the same memory address that var utilizes to store its data. In other words: ptr and var are located in their own respective differing memory address, but the data content of ptr is the memory address that var uses to store its own data.
But the problem is, the content of ptr can indicate either both a proper int number (if ptr was actually just a normal int variable) or a valid memory address (if ptr actually is a pointer). For example, the content of ptr can be 0x000004D2. This can either indicate the number 1234 or the memory at address 0x000004D2. Therefore, you cannot reliably tell if a variable is a pointer by examining its content alone."
No comments:
Post a Comment