-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Aug 13, 2009 at 08:42:18PM -0300, Ismael Luceno wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> El Wed, 12 Aug 2009 11:01:01 +0000
> We could do the same for write-access as long as we don't have
> threads...
> (...)
> I would prefer to keep the single thread model. Multi-threading adds
> too much complexity.
Yeah, that was not a vouch for multithreading. I was just trying to say that
I'd think it would hide enough complexity to allow us to deal with problems
like that later on. Multithreading was just an example.
> I don't think having an API for each db is a good idea...
How many DBs do we have? We could just pass around the list head or something,
just like glib2 does with its list handling functions.
Btw, why don't we just do a static link to some parts of glib2, or even carve
them out from the source code? Perhaps code reuse (theft :D) leads us on a
faster way to something. Just a wild suggestion.
> Another option is to simply pass the list head back through a function
> (which maybe should be hidden by macros), but that's not as clean as I
> would like...
As I'd say, just make it a struct or something, because the programmer
shouldn't fiddle with it as long as he doesn't know what he does, and if he
does, well, don't whine when it breaks. (Yes, I'm a Perl programmer.)
-- Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
iEYEARECAAYFAkqFGkwACgkQhS0drJ3goJKmNgCgijWRQWQuQieg7JMHbyR44MPu
2ysAn15tNCBN4XgAKzysnpiibfnnRDRg
=eKsr
-----END PGP SIGNATURE-----
--
_______________________________________________
Initng mailing list
[email protected]
http://jw.dyndns.org/mailman/listinfo/initng
