Re: [Cgdb-devel] New libraries for CGDB

[Ronald Landheer-C. <ro...@la...>]

Bob Rossi wrote:

>On Wed, Mar 03, 2004 at 09:21:47AM -0500, Peter Kovacs wrote:
>  
>
>>On Tue, Mar 02, 2004 at 10:10:01PM -0500, Bob Rossi wrote:
>>    
>>
>>>As I am starting to think about the implementation of libkui, I am
>>>running into walls. It looks like CGDB is going to need some basic C
>>>data structures. It is probably unreasonable to think CGDB won't need
>>>basic data structures like linked lists, hash tables, ...
>>>
>>>So, we have 2 options. Use a C library someone else has already written
>>>and tested, or go through the pain of writing our own, and making a new
>>>project, libadt ( or something ). I would really like to know what
>>>everyone thinks we should do here.
>>>      
>>>
>>I would suggest you don't make yet another library.  glib has all those
>>data structures you want, and I'm sure there are more just like it.  I
>>really don't think we need to waste our time, writing, debugging, and
>>testing another adt library.
>>    
>>
>
>Ok, it seems like we are interested in the glib data structures. At one
>point, I believe Ronald said that the library didn't port to Cygwin. I
>propose that we "rip out" the code we need from Glib. This will get us a
>minimal implementation of the functions necessary. Then when we think we
>need to update, I'll merge in the newest version. 
>
>I'll look into how coupled the ADT's in Glib are to other part's of Glib
>that we are not interested in. Hopefully if we just get these data
>structures, there will be nothing to port ( no OS related code ).
>  
>
There currently is no glib port for Cygwin - that doesn't necessarily 
mean that it can't be ported. Perhaps it already has been ported as part 
of the Cygwin-GNOME (or GNOME-Cygwin - I forget) project, but I don't 
know that. What I would personally like to avoid is external 
dependencies on code that is out of "our" control, which would make it 
more difficult for porters (such as myself) to get the necessary patches 
upstream.
(In any case, glib does not build OOTB (on an OOTB Cygwin install) and 
apparently has some external dependencies of its own).

Again, for the data structures you want, I need the same ones for the 
Jail-ust project and am writing equivalents of what I wrote in C++ in C. 
The interface of the hash implementation won't change when I write it in 
C (there will just be a new type added and the C++ code will be put in 
defines to handle the absence of a C++
compiler (or the absence of interest in the C++ parts).

I'm willing to bump the priority - I have a few weeks of programming 
time on my hands anyway - and I would personally be very interested in 
having a somewhat larger userbase than that of Jail-ust for this library 
- mostly because Jail-ust is a nascent project with no users at this 
time except for its components.

Just me two cents :)

rlc