> For explicitiness, we could use the __direct__hash and compare functions in > g_hashtable_new_full, which would let us get rid of few (gpointer) casts. > > Furthermore, does the (udp_data->)data leak in rm_udp_data (struct arglist *, > int)? If so, one could either implement a udp_data_free and pass it to the > g_hash_table_new_full or do it manually in rm_udp_data. > I did not look long enough at the "original" harg_remove (udp_data, name), > maybe it did the same (which might look like a "leak" in the first place).
Looking briefly at harg_removet, I guess it was a leak in the first place. _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
