--- Nadim Khemir <[EMAIL PROTECTED]> wrote: > Brian and JMD, Could you please expose in details what you want to do > and > why?
My plans for the introspector are slowly turning into reality. http://introspector.sourceforge.net/class_diagram.htm > Some real examples would be great. The point is that there is a huge amount on information locked up into the existing software systems memory. This information needs to make usable without having the reinvent the software. Example questions are : what people use this function? What lines of code need to changed in order to rename this field in a struct? What caused this file to be made? What things start with the id "tree_c*" > > > From: James Michael DuPont [mailto:mdupont777@;yahoo.com] > > > My advice is don't, even if I understand why you want to do that. > > Please explain, > > The OS group where I work also have the nice job of maintaining the > make > system we use at our job. I've been fighting with make systems > lately, > especially Cons (which is good but limits my thinking possibilities). > I also > thought about writing a make system or modifying something existing, > From > the private discussion I've had with some cons users, I'd say that > there are > other that want to write a make system that is _not_ 'make'. I have been doing alot of repacking of the modules needed for the DIA tool. There are lots of different makefiles, different configuration systems, it is very painfull. http://introspector.sourceforge.net/dia_win32.htm We need a common interface for extracting data out of all these tools. > > IMO make systems are complex and need to be tested quite thoroughly. > I don't > say it is neither fun nor possible; it is just a lot of work. I dont want to build new systems, but to tap into older ones. > > > There are not enough diagnostic tools for the automake or the > debian > > make, or even MakeMake in general. > Cons and MPP are good for that. Are the compatible with existing makefiles? Cons is not, I need to help debug existing makefiles. > > > We need to provide some standard visualization/gui tools that can > read > > dumps from various build systems using a standard input language. > > Wooowww, I stop the warnings to state my admiration for your courage > (foolishness ;-). If I can't convince you to not develop something > new, I'd > be glad to help (foolishness is cool). This project started out as an interface into the gcc and is growing into a complete free software re-engineering framework build around the idea of data extraction. Please do help, join the mailing list, help test the modules, help build interfaces. mike ===== James Michael DuPont http://introspector.sourceforge.net/ __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/
