Re: [gomd-devel] Re: more thoughts

[Matthias Rechenburg]

Hi again,

here my thought about using c or c++ ;)

To my mind we should use c++ for both, the gomd and the libgomd.
As i see it the libgomd will "only" contain functions/methods to get
values from the gomd-daemon. So it should use the commonc++ lib.
The gomd itself will also use the commonc++ lib too to provide
these values on a socket. It will get these values directly
from the proc-interface (or from somewhere else).
So the gomd will have its own class+methods to get these values.
These methods will be implemented in pure c and providing 
an OO interface for using it "inside" the gomd.

.... the gomd doesn't need to be linked against the libgomd as i thought 
before.

What do you think ??

On Donnerstag, 13. Februar 2003 22:09, Ramon Pons Vivanco wrote:
> On Thu, 13 Feb 2003 09:40:53 +0100, Mirko Caserta wrote:
> > I was thinking about avoiding all the problems related to g++ name
> > mangling writing the library in pure C. To me it makes more sense writing
> > the library in C and using it in the daemon which will be written in c++.
>
> This is a good question.
>
> > After all, all libgomd should do is reading some files from the /proc
> > interface which probably is not going to need to involve the complexities
> > of OOP.
> >
> > What do you think?
>
> Pros to C:
>       * userland and openMosix written in C. If we finally merge gomd + 
> libgomd
> + userland C will be nice

right

>       * Unix and Linux are written in C
>       * Easyest

;P disagree, hehehe

> Pros to C++:
>       * High level
>       * Iterators
>       * libcommoncpp
>       * STL
>
> Really, I don't know ...

.... we all will decide after the discussion.

>
> > > I am thinking of re-creating the gomd-project manually too.
> >
> > You're on your own on this field. I've always had a bad relationship with
> > autoconf/automake :) By the way you pointed out good thoughts to which I
> > agree.
>
> This will be a nice moment to start learning automake/autoconf (even for me
> !!)
>
> > > ...........and for sure we can use both of the manual generated project
> > > in every editor or/and kdevelop. e.g. i can/will generate kdeveloper
> > > project files for the manual created project.
> >
> > I agree. Each of us uses his own editor/IDE of choice. For instance, I
> > use Netbeans which has a quite good c/c++ support. It has a memory
> > footprint of about 200MBs but with my 512MB RAM I can afford it :)
>
> Just 2 works:
>       emacs21 rocks !

have fun,

Matt
-- 
E-mail  :  address@hidden
www     : http://www.openmosixview.com
an openMosix-cluster management GUI

I don't make my mistakes more than once. I store them carefully and
after some time I take them out again, add some new features and
_reuse_ them.