Mailinglist Archive: zypp-devel (56 mails)
| < Previous | Next > |
Re: [zypp-devel] Re: [zypp-commit] r8131 - in /trunk/sat-solver/bindings: ruby/CMakeLists.txt ruby/ruby.i ruby/satsolver.rb ruby/tests/ ruby/tests/loading.rb ruby/tests/pool.rb ruby/tests/repo.rb satsolver.i
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Fri, 21 Dec 2007 10:06:02 +0100
- Message-id: <20071221090602.GB8632@xxxxxxxxxxxxx>
* Duncan Mac-Vicar P. <dmacvicar@xxxxxxx> [Dec 20. 2007 23:47]:
Yes, in some parts. The problem with generating from sat-solvers .h
files is the vast amount of internal data being exposed.
Adapting all sat-solver .h files for 'public' and 'private' data
structures might be another approach. But this also needs care, which
I currently put into satsolver.i
All the internal structure properties. And it also makes functions
real instance methods.
Whats the value of having C++ here ? Please explain.
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
On Thursday 20 December 2007 11:19:47 pm kkaempf@xxxxxxxxxxxxxxxx wrote:
Author: kkaempf
Date: Thu Dec 20 23:19:47 2007
New Revision: 8131
URL: http://svn.opensuse.org/viewcvs/zypp?rev=8131&view=rev
Log:
put some love into the bindings
great!
- dont generate everything from .h file, but selectively
Uhm, does that mean we will have to sync by hand?
Yes, in some parts. The problem with generating from sat-solvers .h
files is the vast amount of internal data being exposed.
Adapting all sat-solver .h files for 'public' and 'private' data
structures might be another approach. But this also needs care, which
I currently put into satsolver.i
whats actually needed
what is excluded now?
All the internal structure properties. And it also makes functions
real instance methods.
- add test cases for Ruby bindings
nice :-)
Why did you change cxx to .c when the output is actually a C++ source (the OO
layer is inlined)
Whats the value of having C++ here ? Please explain.
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |