pearcej / cpp4python Goto Github PK

There are multiple occasions throughout the chapter where the Python "turtle" library is referenced with a plural noun and similar issues. They need to be made uniform throughout the chapter, e.g, just "turtle", SANS QUOTES.

It generally works, however, the "grid" doesn't have the correct checker pattern.

All parsons problems, active codes, and matching problems across Chapter 2 are in checkpoint. Instead, they should be labeled as reading questions or exercises, and the active codes should be without checkpoints.

In this question:
Q-4: T/F: It is necessary to have an else statement after an if statement?
It should read as the following because it is not a question:
Q-4: T/F: It is necessary to have an else statement after an if statement.

After the last code activity in Section 2.3, this statement is made

The declaration int theSum = 0; creates a variable called theSum and initializes it to hold the data value of 0.

theSum is initialized to a value of 4, not 0.

Chapters One summary section is missing along with the self-check questions and the active code.

cppds

cppds-v2

At the end of the first paragraph of Section 1.4.7 there is the text

For example, in the code above, the integer input is doubled and then displayed!

The input is a float, not an integer.

Figure needs alt-text as an accessibility feature. The text should be as succinctly descriptive as possible in regards to what the figure actually shows.

The output of the function in Q1 in section 3.2 should be "Hello, world0" infinitely many times because the instruction is:
cout << "Hello world" << counter << endl;
Therefore, NONE of the answers given is correct, so option D is correct. Either fix option C or change the correct answer.

ActiveCode (cturtle_geometry_ac_1) in geometry_shapes_stamps is cleared so fast that I can't see it.

In Section 1.6, the answer for Q-13 states

The correct statement would be "cout << x;" or "std:cout x;" but the insertion operator is certainly needed.

The << is missing from the second example. I.e., the answer should read

The correct statement would be "cout << x;" or "std:cout << x;" but the insertion operator is certainly needed.

All parsons problems, active codes, and matching problems across Chapter 2 are in checkpoint. Instead, they should be labeled as reading questions or exercises, and the active codes should be without checkpoints.

Chapter 4 mentions that some operators such as =, [], () and -> can only be overloaded as member functions of a class and not as global functions.

All parsons problems and matching problems across Chapter 1 are in checkpoint instead, they should be labeled as reading questions or exercises.

Page 8.6 has no questions, but it should have some to act as a reading comprehension check. One or two questions should be fine.

The interactive part for section 1.4.6, which refers to a replit sourced iframe, (looking at the HTML source) does not work when using incognito mode. It looks like this;

Students find make_neat() confusing because they are not looking at the files. Before this interactive code segment, add non-interactive code blocks (using ::) into the make text of the book that better describe the goal of the code by showing how to code looks beforehand in one block and afterwards in another.

has a couple of problems:

• used the term reference instead of pointer.
• discussed classes which are not referenced at all in this textbook

CollectionData/glossary also has some non-parallel terms.

After the code activity in section 3.3, the sentence "In the example above, the hello world! statement is executed 10 times." should not have an exclamation point after "world".

Section 3.3. on For loops uses arrays and vectors before these are introduced. Do the following:

1. Move all of the examples that use arrays and vectors to the collections chapter
2. Create new for loop examples that do not leverage collections.

Here's the link: https://runestone.academy/ns/books/published/cpp4python/IntroCpp/firstcppprogram.html#summary

The question reads "Q-12: True or False: Both Python and C++ support multi-line comments. In C++, they begin with /* and end with */."

According to the programmed answer, it is False because "Sorry, both languages do support multi-line comments, but they look different.", but the question doesn't imply that multi line comments in Python start with /* and end with /, it only states that "In C++, they begin with / and end with */" which is true.

Proposed solution: Either change the wording of the question (e.g. remove "In C++,") or change the solution.

All parsons problems, active codes, and matching problems across Chapter 3 are in checkpoint. Instead, they should be labeled as reading questions or exercises, and the active codes should be without checkpoints.

Figure Figure 2.3 has a 9 in varN. This is good.

However, the code snippets put a 100 into varN. This is confusing. Change the value of varN to 9 to better coordinate with image. (This needs to be changed in at least 2 places.)

I LOVE the idea of this example!
ActiveCode (cturtle_practical_example_cpp) has a few bugs. It timed out with the loop set to 8. It also is not showing the whole graphics window. Maybe restrict the tiling to a smaller area of the graphics window?

just says #include - should be #include <CTurtle.hpp>

’

Change this https://repl.it/@CodyWMitchell/File-Handling-3 not to take any inputs, without changing the results.

In Section 2.5.3 of the book, there is a typo in the first code block (line 703 in /_sources/AtomicData/AtomicData.rst):
cout << "Pointer ptrx points to " << &ptrx << endl;
This line prints the address of ptrx, instead of the address it points to.

I believe the correct version should be
cout << "Pointer ptrx points to " << ptrx << endl;
as in pull request #105.

Please let me know if I'm correct. Thanks

The word Glossary is repeated across the new version of the book at the end of each chapter, mainly in the glossary section.

Refer to the Runestone Author Guide to see how you may actually allow for "dummy" files to read from using the :datafile: directive. Replace with ActiveCode examples.

All parsons problems, active codes, and matching problems across Chapter 5 are in checkpoint. Instead, they should be labeled as reading questions or exercises, and the active codes should be without checkpoints.

Fix Python example of purple square

All parsons problems, active codes, and matching problems across Chapter 2 are in checkpoint. Instead, they should be labeled as reading questions or exercises, and the active codes should be without checkpoints.

Following the original pull request for the chapter, I've noticed some instances of typos throughout the chapter. Specifically, on 8.4, the second sentence has a typo. I'm sure there are others.

Both the Python and C++ code should be immediately visible, preferably with the Python code first. Students should be able to actively compare between and be compelled to run both examples.

In intro-cpp_let-s-look-at-a-c-program.ptx 1.4.3, the parsons problem has a typo. The parsons problem has an unrecognizable word instead of '#include '

Discuss close-to-hardware, memory management, and "industrial-strength" properties of C++ itself as it pertains to graphics.

First of all this is a great book. Thank you for this resource. Is there a way to get a pdf for this book, so that it can be printed?

The summary section in Chapter 2 needs to include self-check questions; as we can see in the following pictures on the old version of the book, the summary section have some self-check questions, but on the new version of the book, that is missing.

The word "asterisk" in the sentence" WARNING: What happens if you forget the asterisk when assigning a value to a pointer and had the following instructions instead?" should be "ampersand":

 WARNING: What happens if you forget the ampersand when assigning a value to a pointer and had the following instructions instead?

The code in this question has the line:
cout << counter * 2 << <<" ";
which will result in a compile error because of the two "<<" in a row. Therefore, either fix the code so that option A is correct or add a "compiler error" option.

In introcpp_introcpp_intro-cpp_glossary.ptx, the matching problem is very long. It is hard to do it simultaneously since the matching problems are not dynamic. As a student who uses the book, I found solving one problem at a time hard. If it is divided into three parts, it will be easy.

From: Orion O. Musselman

On this page (https://runestone.academy/runestone/books/published/cpp4python/Input_and_Output/InputandOutput.html) it was stated that "execution of the following statement will write the number 25, a space, the number 15, and another space into the out_stream output stream," when the example below used the endl constant, leading me to believe that either the code example or the text was mistyped.

Activity 13 in the pointer chapter is supposed to demonstrate a dangling pointer, but the pointer is not dangling. This needs to be "fixed"... i.e. it needs to be broken.

Activity 3 Drag-N-Drop (cturtle_dnd_1) in turtle_and_turtlescreen is too long. I recommend breaking into 2 or 3 exercises that are coherently separated. On my Berea College laptop I literally cannot get to the bottom of the huge list. Also, there are two turn to the lefts and no turn to the right...

I believe this is the same issue as #42 I think students will most likely not scroll through the code which is going to cause more confusion. We should add the code (using ::) before the repl.it section.

Chapter 4 has some extra concepts in the glossary related to classes and what "friend" does, it says it is a function that can access the private data members of a class.