Re: Fwd: I released the refactoring tool

I chose Sqlite because it's a lightweight and high performance database
used for desktop applications. Its database is just a single file, and is
space-efficient. Currently, CEDET stores its database in textual sexp
forms, and this takes up a huge amount of diskspace on large projects (I
tested it once). I think the built-in database is good as it is, but we
need a better one, just as Semantic needs an parser from a real compiler
for accurate parsing. Actually I think that if we could delegate heavy
lifting tasks (like parsing and database) to external programs, it would
make it easier both for CEDET maintainers and users to make it work
properly.

Of course, CEDET framework is still very useful. Not many editors has a
good parsing framework like CEDET that allows actual language development.
But due to the limitation of Emacs Lisp interpreter, it's best to use for
languages at small scale. For example, applications that have its own
configuration syntax (i.e. Apache server, DHCP server) would be beneficial
to create a major mode using Semantic for language awareness, than simply
using regexp for highlighting, or writing the whole parser manually like
js2-mode. Or scripting languages that are usually used individually in
separate files (i.e. bash scripts).

On Tue, Feb 17, 2015 at 4:50 AM, David Engster <[email protected]> wrote:

> Tu Do writes:
> >> That's my plan as well, using libtooling.
> >
> > That's great if you can take care of this. I would not want to wait
> forever
> > until we are permitted to use GCC :)
>
> Yes, I've given up on using GCC.
>
> >> Not sure what you're planning here. Do you want to replace Semanticdb
> > completely, or do you want to make Sqlite a back end for Semanticdb?
> > Hard to say how much that would gain, since AFAIK, there's no efficient
> > way to transfer large amounts of data between Emacs and Sqlite.
>
> [...]
>
> > - Async: this alone is worth it.
> > - Code querying with a popular and robust language. This will enable
> people to
> > write small utilities using SQL, such as code metrics or statistics.
> With an
> > actual database engine, we can do operation like searching for all
> functions
> > that call current function, accurately; or all files that include a
> particular
> > header files; or see all the included files that contain the definitions
> of
> > tags in a current class; or simply creating a class index of a project
> (similar
> > to what Ebrowse does, but for large index, it took Emacs really long to
> load
> > all).... All of this can be delegated to a fast database engine. All we
> need is
> > a properly designed database for tags.
>
> I agree this all sounds nice. I'm skeptical because I wouldn't want to
> see CEDET's complexity increased even further. Maintaining a second
> database backend for Semantic would be a very big burden, and I feel
> we're already struggling just keeping up with Emacs development and
> maintaining the status quo. In my opinion, CEDET's main problem is not
> that it cannot deal with large code bases, but that it's still not
> reliable enough and too complicated to set up. This should not
> discourage you from trying Sqlite, of course.
>
> -David
>

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk

_______________________________________________
Cedet-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cedet-devel