Re: [Somelib] More changes

[Thomas M. <tma...@ze...>]

John Palmieri wrote:

> Thomas Matelich wrote:
>
> >The solution was to write my own map, which was
> > surprisingly easy.  Only a few real lines of code.  This change has been
> > ifdef'ed for windows only and the API remains the same.
> >
>
> Hmm... is your map derived from std::map? I want to add functionality soon
> that passes in a map to a method to search for multipule object matches.

No, I had to drop std::map completely.  I could make a constructor that takes
a std::map.  Essentially the problem is when the map is created on one side
and used on the other.  Although, both sides do share the same memory space,
the static members of template classes seem to exist on both sides.

> There is only one Makefile for the main distro and simple Makefiles for the
> examples.  The reason for this is I don't use recursive makes but instead
> include vars.mk and rules.mk from each directory.  This creates a faster
> build.  Tell me what errors you are getting and I will fix them.
>

Ok, makes sense.  So the errors I'm getting on hpux are UserConfig.h can't
find config.h, things can't find boost and apparently your test for if it is
hpux doesn't work because USE_SOME_HPUX_SL is not defined.  I'll try it out on
Linux see if I can get it to work there.  Is the directory for installation
configurable?

> > 3) Doxygen also generates latex, man, and rtf formats, should I add
> > those to CVS?
>
> Hmm...no but add them to the tarballs.  We should automate their creation
> with a make docs and make docs_install.

make docs calls doxygen doxy_config.

> > Code:
> > 1) Formatting.  I was going to run astyle on it.  Are you CoreLinux++
> > guys using a pretty printer?
>
> I used lint once and hated it but anything taht increases the readability
> of the code I am all for.

astyle.sourceforge.net is cool if you don't hit one of the bugs.
Unfortunately there doesn't appear to be any development being done on it.

> > 3) Name analysis.  Are these the names we want for our classes
>
> Yes.  I think we need to run this through beta testers and develop a
> vocabulary (Perhaps the Info stuff should be called a catalog and
> getCategory should be overloaded to handle both the simple catagory and
> multipule category gets).  Also intern names we use for the maps should be
> obfusicated so as to avoid name clashes with someone perhaps using
> "category" as one of their categories.
>

ClassProperties and LibCatalog?  I'll change the classname and category keys
to something peculiar.

> > 4) Namespaces.  Pretty please :)
>
> I just took a look at the white paper for Itini stuff from RedHat (C++
> wrapper for GTK+).  They use namespaces and I think so should we.  Screw
> all the non complient complilers use g++ :)

Music to my ears.  I will change the SOME_BOOST stuff out of a macro and all
SOME...'s will become SOME::...'s

> > 5) Error conditions.  Currently a few exceptions.  Do we like this?
>
> The lib itself should never coredump (it does when it can't find a library
> on linux).  Users objects we have no control over.

How do you feel about exceptions?  I know a lot of people don't like them, but
they are standard compliant, and I think the errors we send out are
exceptional.

> > 6) Write the searchForLib func.
>
> Yes.

Actually, I have no idea what I intended searchForLib to do.  What does it
sound like to you?

> > 7) Do we want a getAllLibsInThisDirectory type function?
>
> Yes but it should just be the same method that loads the librarys.  The
> method should just check if the agument given is a file or a directory.  We
> should also perhaps add the ability to load libraries defined in a an
> enviornment variable and a text file.

Sounds good to me.  I'll put it on my list.  Though, what if they accidently
pass in a dir and load 300M of libraries?

> > What did I miss?  Should we make a beta dist next week and make a
> > freshmeat posting?
> >
>
> I was thinking the same thing.  Beta testing should be concentrating on
> getting ideas from outside developers and then after we freeze the
> development a final beta should be packaged and all bugs fleshed out for
> 1.0.  Wow my first 1.0 open source project.
>
> I'm interested to know what projects you are using this in.  For me I am
> using it in Snaglepuss - open source multimedia development. And OnCue -
> Snaglepuss' scripting enviornment.

So far I've only used it in my own version of CppUnit (the XP unit testing
framework).  I made it so tests can be stored in shared libraries and loaded
at runtime.  This is nice because I can now ship my tests and not have their
existence affect the customer.  I hope to clean it up and get management to
let me release it.  The neat thing is that each test case has a static member
which returns a suite of tests and I was able to do some "Test Defines" macros
to call that static and send it's return back to the host app, rather than
calling a constructor.


--
Thomas O Matelich
Senior Software Designer
Zetec, Inc.
sos...@us...
tma...@ze...