do_pgr_MY_FUNCTION_NAME is called in the c code from the code we can clearly see that it reads the data specified in the sql statement. We can see that some of the arguments that are passed to this function are pointers.
So now from the do_pgr_MY_FUNCTION_NAME we get data as pointers along with the size. The idea is to convert this data which is given in terms of pointers to cpp structures.
Here was a conversion of data in terms of pointers to standard cpp structures so the pgr_MY_FUNCTION_NAME is being called with all its arguments being standard cpp containers/structures
About header files the files with a .h extension are called header files it contains function declarations
the function is not actually implemented there. the prototype of the function is specified there
Prototype defines: 1.function name. 2. its arguments and their types. 3. return type.
We see that the driver(.h) is included in the c code
Now that we have the prototype defined in the .h file, the actual function implementation is done in .cpp file
We see that both the names are the same in the following links Contraction.sql, CMakeLists.txt. In the sql file we specify the name of the object library.
do_pgr_MY_FUNCTION_NAME
is called in the c code from the code we can clearly see that it reads the data specified in the sql statement. We can see that some of the arguments that are passed to this function are pointers.do_pgr_MY_FUNCTION_NAME
we get data as pointers along with the size. The idea is to convert this data which is given in terms of pointers to cpp structures.do_pgr_many_to_many_dijkstra
has some of its arguments as pointers.pgr_MY_FUNCTION_NAME
is being called with all its arguments being standard cpp containers/structures