My first question was do you make design decisions (e.g., chose one indexing
algorithm over another) based on attributes such as --
1. How deep is the directory tree
2. what is the distribution of file sizes
3. how many media v/s text files are there
and other such distributions
For those who deal with gobject API, when you pass a string (char* or
const char*) to an API function, whose responsibility is it to free
the string ? What is the usual practice ? Is there any way to
distinguish methods that take a string and own it and methods that
make a copy of the string so
Hi,
On Thu, Apr 3, 2008 at 1:34 PM, D Bera [EMAIL PROTECTED] wrote:
For those who deal with gobject API, when you pass a string (char* or
const char*) to an API function, whose responsibility is it to free
the string ? What is the usual practice ? Is there any way to
distinguish methods
