שאלות ותשובות - Homework Assignments - HW4 Frequently Asked Questions - Homework Assignments - HW4 Вопросы и Ответы - Homework Assignments - HW4 أسئلة وأجوبة - Homework Assignments - HW4

		.. (לתיקייה המכילה)

		Dry
	What do you mean by "generic collection" ("אוסף גנרי")? I suggest you solve the dry part once you learn about iterators and generic collections in class. Anyway, if you wish to start earlier, here's a brief explanation. A "generic collection" is represented by two iterators: one points to the beginning of the collection, and another to its end. The second (end) iterator does not point to an element inside the collection, but one position further (similarly to std::vector::end()). You can assume that both iterators refer to the same collection, meaning if we advance the first iterator over and over again, we will eventually reach the second iterator. You can also assume that the iterators provide all functionality provided by the STL iterators. As an example, the implementation of a function that receives as an argument a generic collection, and returns its size, would look like this: template <class Iterator> int getSize(Iterator begin, Iterator end) { int size = 0; for (Iterator i = begin; i != end; ++i) { ++size; } return size; } Do we have to write code in 1 ב? Yes. In 1 ב, can we assume that all elements in collection are distinct? Yes.

		Wet, General
	How do we use ASSERT_THROW, and ASSERT_NO_THROW? ASSERT_THROW is used to assert that some function call throws an exception of a given type. For example, since we know that constructing a Pokemon with a negative level should throw an exception of type PokemonInvalidArgsException, we can test it as follows: Pokemon* pokemon; ASSERT_THROW(PokemonInvalidArgsException, pokemon = new Pokemon("pikachu", 2.5, -2)); Whereas since calling the constructor with valid arguments should not throw any exception, ASSERT_NO_THROW(pokemon = new Pokemon("pikachu", 2.5, 2)); should pass successfully. How to set and verify the new g++ version for the assignment? In order to use gcc/g++/gfortran 4.7.1, you should run first: source /usr/local/gcc4.7/setup.csh # for CSH and TCSH or: . /usr/local/gcc4.7/setup.sh # for BASH and SH verify version by: gcc --version gcc (GCC) 4.7.1 Please note that this change will expire after you log out. Refer to tutorial #2 to see how to make this permanent. How many Trainer files should we submit? Should we submit two versions: one for part 1, and another for part 3? You should submit only a single implementation of class Trainer (trainer.cc, trainer.h). The implementation should be the one obtained after adding the changes in part 3.

		Wet, First Part
	You say that the level of the Pokemon is constant and does not change, on the other hand, we are supposed to implement the assignment operator. Do we have to declare the level as a const member? No. Saying that a level would not change does not imply that level should be declared as const int. Since you have to overload operator=, which must also assign the level, level cannot be declared as const. We just wanted to make it clear that level never changes (except for assignments).

		Wet, Second Part
	Do we have to write unit tests also for KGraph? Yes. Can we use STL for implementing the KGraph? Yes. Which exception should Connect(key,key,int,int) throw when both keys are equal? Since we have not defined an exception for this matter, you can assume the user does not make such call (you can say that the behavior of the function in this case is undefined).

		Wet, Third Part
	When the leader of a gym is the only trainer in the gym, and he leaves, does he remain the leader of the gym? No. The leader of the gym must be a trainer in the gym. Therefore, in this case, the gym will have no leaders. How is the score of a team computed exactly? The score of a team consists of three parts: - Battles: this part of the score is the only one that is cumulative (מצטבר). Whenever a player from the team wins a battle, the score increases by 2, whenever a player from the team loses a battle, the score decreases by 1. - Leaders: number of leaders from the team in the **current** state of the game x10 (players that were leaders previously do not count). - Levels: the sum of the **current** levels of all players from the team. Is the level of an item always an integer? Yes. Do and Don'ts regarding class Trainer: Don't: Change the definition of functions we have defined in the first part (we are going to test them). Do: Basically anything else. What happens when a trainer moves through a loop from and to the same location? In this case, the system must behave as if the trainer left the location, then arrived at it. Will you try to insert locations to the world using World::Insert? As mentioned, World should provide all functions provided by KGraph<std::string, Location*, 4>, this includes KGraph<std::string, Location*, 4>::Insert(std::string, Location*). But, Since the creation of a Location can be done only through a subclass, which you have declared and implemented, we cannot test calls to World::Insert in a unit test. Nevertheless, we are going to check manually that your program handles such calls. How should World::Insert(std::string) behave? What should be the default value for the Location*? You can assume the user does not call World::Insert(std::string) but only World::Insert(std::string, Location*). Namely, you can choose the default value to be whatever you want.