TP_13 exo2: use C99 struct initializers

[TD_C.git] / TP_13 / exo2 / lib / coordinates.c

diff --git a/TP_13/exo2/lib/coordinates.c b/TP_13/exo2/lib/coordinates.c
index 883f11962521c4561d197b67da734490a003eed6..ef80ba9d8b8bfe77da68c9d81fb73caddc2874e1 100644 (file)
--- a/TP_13/exo2/lib/coordinates.c
+++ b/TP_13/exo2/lib/coordinates.c
@@ -18,18 +18,13 @@
 
 #include "coordinates.h"
 
-void init_coordinates(coordinates_t* coordinates_array) {
+void zero_coordinates(coordinates_t* coordinates_array) {
 
     for (unsigned i = 0; i < MAX_COORDINATES; i++) {
         coordinates_array[i] = set_coordinates(0, 0, 0);
     }
 }
 
-void reinit_coordinates(coordinates_t* coordinates_array) {
-
-    init_coordinates(coordinates_array);
-}
-
 coordinates_t set_coordinates(int y, int x, unsigned type) {
     coordinates_t new_coordinates;
 
@@ -40,10 +35,11 @@ coordinates_t set_coordinates(int y, int x, unsigned type) {
 }
 
 /* FIXME: Does it worth doing a coordinates_t get_coordinates(int y, int x, unsigned type); helper function? */
-/* Or a int get_coordinates_x(int y, int x, unsigned type); helper function? */
+/* Or a int get_coordinates_x(coordinates_t coordinates); helper function? */
 
 /* the function do a lot of sanity checks before adding new board elements,
- * hence the loop. moving the checks in the main loop is also possible */
+ * hence the loop. moving the checks in the main loop is also possible.
+ * for now, just branch in the main loop given this function error value returned. */
 unsigned add_coordinates(coordinates_t new_coordinates, coordinates_t* coordinates_array, unsigned round) {
 
     /* valid coordinates are in the [1-3] range */