Hi!

I've seen that people started to break ABI in trunk so it is probably
going for the 2.4 release. In connection to that I have a question about
the v3.0 project [1] and experimental branch [2].

Experimental branch has not seen any activity in a very long time, so is
it still pursued? Or should all the changes just go incrementally into
the trunk?

My guess is that all API breaking changes are still not allowed in trunk
(ABI breaks would be allowed for 2.4, but API breaks only for 3.0). If
so API breaking changes would have to go into experimental or some new
branch.

I've started to clean up compiler warnings (cleaning up as fast as they
are committed ;) and would like to move on from there at some point. In
particular, I'm interested in the following topics:
- Compiler warnings, general cleanup
- Using size_t for counts and sizes etc.
- Indexing change (1 to 0 based)
- Boost's shared pointers or equivalent for automatic reference counting

Are these things ok for the trunk?

I haven't gone trough the stuff in the experimental branch, but in any
case that would have to be rebased on the current trunk. I might do that
or just create a new branch in my git-svn repository.

By the way, is a general migration to git still off the table?


Regards,
Reinis

[1] http://openbabel.org/wiki/Version_3.0_Projects
[2]
http://openbabel.svn.sourceforge.net/viewvc/openbabel/openbabel/branches/experimental/


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenBabel-Devel mailing list
OpenBabel-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbabel-devel

Reply via email to