Re: [Lxr-dev] VHDL support and other stuff
Brought to you by:
ajlittoz
From: Robin T. <Rob...@te...> - 2001-11-15 13:37:25
|
Hi Malcolm, > What I half-implemented last night does the following: I do not see it in CVS yet ;-) BTW, is there any way of getting head revision out of the SF CVS by tarball. > 1) Expand indexes.type to an int field > 2) Create a declarations table containing declid (int) and declaration > (char(255)) If you use two ints (one for the language and one for the id) each language can have its own "namespace" (my original major, minor idea). The impact is small if using two small ints. > 3) Each language now maps the ctags types output/whatever other type > info it has to an int (currently hardwired) > 4) Index::index() now stores the type field as an int > 5) Ident then joins declarations.declid to indexes.type to get the right > string for display. > > If we want to record the language the identifier was found in, it can > either go in the files table, or in the indexes. Putting it in files > implies that there is a 1 to 1 mapping from files to languages, which > while currently true may not always be (think webpages with scripting in > multiple languages :- ) . Putting it in indexes is a little redundant > at the moment, especially since indexes is one of the biggest tables. Given the current bindings from filename to language module, it makes sense to put it into the files table. Your webpage example is pretty scary, but a special language module should take care of this. Unless the page is preprocessed in some hairy way, there's a parser going to read it at some time. > The licence is the number one problem. Cleaning up the code so it runs > on non-gcc platforms would be good, but it's not essential since gcc is > so widely available. I checked up on the Alliance toolkit. The parser is divided into two. Behavorial and structural, and there's lot of language (like variable) not supported. It is a parser that is almost but not quite entirely unlike a VHDL parser... The good news is that the VAUL parser is derived from the parser i also used, so all I have to do is to recreate my special parser from the VAUL source and we're in GPL. Robin. -- ASIC Design Engineer Tellabs Denmark A/S Direct: +45 4473 2942 rob...@te... |