[Parted-edge] C++ bindings: directory structure

Debarshi 'Rishi' Ray debarshi.ray at gmail.com
Wed Feb 21 11:51:12 UTC 2007

Hello everybody,

I am hoping that the Libpartedpp guys are here too.

Before actually merging/moving the files from libpartedpp with that of Parted,
I would like to discuss the directory structure we are going to use for the
language bindings.

Libpartedpp has 'doc', 'src' and 'test' subdirectories in the root sources
folder. The 'src' directory has both the C++ header (.h) files and C++ source
(.cc) files lumped together. There is no subdirectory to separate the two.

On the other hand, PyParted has no subdirectory in its root sources directory.
All the files are present in the root location itself.

I have thought about the following scheme:

a. Include/import files: include/partedpp to keep the C++ bindings' header
   files. A similar scheme can be followed for the PyParted headers also. An
   alternative can be include/parted/partedpp.

b. Other sources: The actual C (from PyParted) or C++ (from Libpartedpp) files
   can be kept in bindings/python and bindings/cpp. An alternative can be
   libparted/python and libparted/cpp.

What is your opinion?

Happy hacking,
GPG key ID: 63D4A5A7
Key server: pgp.mit.edu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/parted-edge/attachments/20070221/22663882/attachment.pgp

More information about the Parted-edge mailing list