|
From: | Lennart Borgman (gmail) |
Subject: | Re: What IDE features are in CEDET? |
Date: | Sat, 26 Apr 2008 00:09:03 +0200 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 |
Eric M. Ludlam wrote:
If you suspect the existing nxml parser output could be translated into the same style of output as Semantic's tag structures, that can work, but I'm not entirely sure what would be done with the results since xml is flexible enough to cause every schema to need it's own translator into Semantic tag format.
I no nothing about the details. What I thought was that Semantic (or perhaps more the user interface part of it) could ask nxml-mode for the state, completione possibilities etc, whenever needed.
Semantic has incremental parsing also, but only have a full pass has been done.
That reminds me of that Emacs font-lock can do a second pass where context is taken into account. (If I have understood things correctly.)
There was a long thread on this topic in the address@hidden mailing list. Semantic's mode targeting is done using "mode-local.el" which is part of CEDET, which allows simple context switching between language features in a single buffer.
Seems like a needed feature.
You are talking about multiple languages in a single buffer which is different.
Yes, but sometimes you can have view the buffer content either way. For example a buffer containing a php file can be viewed as either just consisting of php code (which of course is a valid view) or as some part containing xhtml and some containing php script code.
The advantages/disadvanteges is of course those you have mentioned. I mention this just to make the concepts more clear.
[Prev in Thread] | Current Thread | [Next in Thread] |