Re: [Cgdb-devel] New libraries for CGDB
Brought to you by:
bobbybrasko,
crouchingturbo
|
From: Bob R. <bo...@br...> - 2004-03-02 23:49:53
|
On Mon, Mar 01, 2004 at 02:42:33PM +0100, Ronald Landheer-Cieslak wrote: > Bob Rossi wrote: >=20 > >Hi, > > > >It's been a long time. However, some of the developers of CGDB are ready > >to start another round of development, which will make CGDB's interface > >much more VI compatible. > > > >There will be several new libraries created to ease the task of > >implementing CGDB. libkui will be one of them. This stands for "key user > >interface". It will be the library responsible for catching user > >commands. For example, when you hit "5Control-wj" in vim, you expect vim > >to move you down 5 windows. Well, libkui will be responsible for getting > >these sequences and returning what command the user requested. > > > >There will be several other libraries created and talked about in the > >near future. I am proposing we place all of the new libraries in > >cgdb/lib. This will be a new directory. Each library will get a > >directory in cgdb/lib. For example cgdb/lib/kui. Finally, each of these > >directories will have a src/ and inc/ which implements the library. So, > >for libkui I will add > > cgdb/lib > > cgdb/lib/kui > > cgdb/lib/kui/inc > > cgdb/lib/kui/src > > > >Does everyone think this is reasonable? If so, I'll add this > >infrastructure to the CGDB CVS tree. > >=20 > > > Seems reasonable enough to me, but for the time being, I'll keep to porti= ng. > However, one thing that may be of interest for cgdb is the container=20 > library I wrote for Jail-ust (also on SourceForge) which I think will=20 > respond to the needs for a hashing implementation discussed here earlier. > If you check it out like this: > $ export CVSROOT=3D:pserver:an...@cv...:/cvsroot/jail-ust > $ cvs login > anoncvs > $ cvs co release-libcontain > you'll get the current version with all of its dependencies (libreplace= =20 > and the architecture-dependent code) Sorry for the long delay. This sounds interesting. Unfortunately, it was written in C++ and cgdb is written only in C. The reason CGDB is written in C is because we believe it should be able to port anywhere that GDB does. This way, it can be used in all the same environments. Thanks, Bob Rossi |