CEDET

Hi,

I am using emacs 24.0.50 (bzr version of july.) It seems that
argument evaluation is not reccursive : I mean following :

>>>  -- CODE 

template subtemp :arg
----
{{MY_VAR}}
----

template temp
----
A comment !
{{>:subtemp}}
----

>>>  -- End CODE 

When inserting subtemp with srecode-insert :arg
(i.e. srecode-semantic-handle-:arg) is launched hence MY_VAR is
set in the dictionary. But when trying to insert temp, even if
it inserts subtemp, :arg does not seem to be set.

Is it normal ? Why ? One could say that I simply have to add
:arg to temp arguments but I don't find that convenient for
some reasons and in particular if one wants to implement
loops. Is it any good reason for which :arg is not set when
subtemp is inserted as a subtemplate of temp ? Or is it a lack
in the code ?

Regards


Pierre

I'm willing to look into this at least to gage the amount of work.
I may even do the work over a few months of time.

Eric, I see wisent-php.wy in contrib directory.
Would this be a good starting point?
As I recall semantic supports two different styles of grammar: bovine
and wisent.  Should we consider using bovine instead of wisent?
Is c.by the default one that semantic uses rather than wisent-c.wy?
Is this reason enough to consider bovine?

Gary, where can I find documentation on lexical analysis of PHP?
The lexical analysis code at the end of wisent-php.wy is really trivial.
Is it that simple?
I took a quick look at the php bnf.
It does not look all that different from others on first glance, e.g.,
python.
Also can you create sample php files for testing purposes?
What I have in mind is really trivial files with just a few lines of
most basic code and working your way to to include more complex syntax.
If you could provide these, that would help a lot.

I have not done any php programming other than reading about it a long
time ago.

I took a quick look at http://www.emacswiki.org/emacs/PhpMode.
I saw a mention of mmm (multiple major mode), which is a package that
I've used for many years, so this is encouraging.

Again I will take a look at at the minimum write up of the issues as a
texinfo file, and even try to implement it.



-----Original Message-----
From: Eric M. Ludlam <eric@...>
To: Gary <cedet@...>
Cc: cedet-devel@...
Subject: Re: [CEDET-devel] PHP support status?
Date: Fri, 06 Aug 2010 18:46:04 -0400

On 08/06/2010 08:19 AM, Gary wrote:
> Eric M. Ludlam wrote:
>> On 08/06/2010 05:01 AM, Gary wrote:
>>> Gary wrote:
>>>
>>>> I see that it seems to be traditional to ask about the current state of
>>>> cedet's php support about once per year. This time it seems it is my
>>>> turn.
>>>
>>> Nobody? :(
>>>
>>
>> Hi,
>>
>> The current PHP support is at a dead-end, with the original contributor
>> uninterested/willing to continue maintenance.
>
> You mean php mode (Aaron S. Hawley is the maintainer of that, and I
>   found him pretty responsive when I had a problem)? Or something within
>   cedet? If within cedet, where is it, please?
>
> I currently use nxhtml for my php editing needs (which includes some
> hacked up version of php mode AFAICT), but it really is only good for
> that - editing. It misses project based support and the like (which, I
> hasten to add, is fine - it is meant as an editing mode).

That is not what I was referring to.  I was only referring to the php 
support for CEDET's Semantic parser.  I'm sure the Aaron is doing fine.

>> There is a second smaller php parser on EmacsWiki, but I don't know what
>> state that is in.
>
> *scratches head* I don't see anything. Even google only finds some
> references to nxhtml:
> http://www.google.com/search?q=site:emacswiki.org+"php+parser"&hl=e

http://www.emacswiki.org/emacs/semantic-php-simplest-grammar.by

>> Two folks from this list were interested in making a new version of the
>> php parser which could be come part of core CEDET
>
> Yeah, I saw that :) It's why I asked what the current status was :)
>
>> and I was hoping they would reply to your email.
>
> Me too :(
>
>> On the whole, there is no active maintainer that I know of.
>
> :(
>
> Do I remember correctly that one basically needs a BNF language
> definition as a starting point? Will EBNF suit?
> http://www.icosaedro.it/articoli/php-syntax-ebnf.txt seems to be mostly
> there, "only" missing a few fixes.

The parsers in Semantic can be made in lots of different ways.  One is 
to convert a bnf into a parser for the 'wisent' parser generator in 
Semantic, which is what the php support in cedet/contrib is.

Any future work would be best served by being developed by people who 
can sign papers with the FSF and assign copyright so that it can be 
included in core CEDET/Emacs.

Eric



------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Cedet-devel mailing list
Cedet-devel@...
https://lists.sourceforge.net/lists/listinfo/cedet-devel

I would just like to point out that semantic has no problem with C/C++
files with 20k lines.  semantic-force-refresh almost always finishes
within a second.  I don't think I've seen it take longer then 3 seconds.

Some files have functions with many thousands of lines each.
Semantic has no problem with these either.

I've seen `M-x bovinate RET' take almost 30 seconds of some of the
largest files though, but this is not due to parsing time but more
it seem to be due to formatting and printing the data.

This is on a fast machine with lots of memory though.


-----Original Message-----
From: Eric M. Ludlam <eric@...>
To: Cristian Zamfir <cristian.zamfir@...>
Cc: cedet-devel@...
Subject: Re: [CEDET-devel] problem analyzing large file
Date: Sat, 14 Aug 2010 10:06:09 -0400

The only thing I can think of is that you may have never given Emacs 
enough time to parse your super-large file, or the file has some sort of 
#ifdef syntax at the beginning of the file that may not be properly 
balanced, thus ifdef'ing out the whole file.

Most buffers are parsed in idle time.  If you press a key it is supposed 
to cancel the parsing to allow emacs to be more responsive.  If a parse 
takes 1 minute, but you never wait that long, it won't finish.

In the senator menu, choose "Force Tag Refresh" to parse the file.  The 
command

M-x bovinate RET

will dump the raw tag list if you need to inspect it.

Eric

On 08/13/2010 05:35 AM, Cristian Zamfir wrote:
>
> Hello,
>
> I am using cedet for a rather large repository and I noticed that it works for some files but not for others. One of the files for which I cannot use ia-fast-jump at all has about 4.5K lines, and I wonder if this is the cause of the problem.
>
> I enabled some debug info (see below) and I understand that this file shows up as having no #include, but that is not true.
>
> Moreover, if I delete the entire .semanticdb dir and try to jump to the definition of a symbol form this file, semantic immediately gives up and says it cannot find a suitable jump point. For the rest of the (smaller) files, it starts parsing.
>
> This seems to point out there a limit for the file size. Is this true?
>
> Is there a way I can see more debug info?
>
>
> Here is the debug info:
> -----------------
>
> Unable to find prefix KModule.
>
> The prefix lookup code threw the following error:
>    (error "Cannot find definition for \"KModule\"")
>
> To debug this error you can do this:
>    M-x toggle-debug-on-error RET   [ Do It ]
> and then re-run the debug analyzer.
>
>
> Local Scope Information:
>   * Tag Class Constraint against SCOPE: nil
>   * No known parents in current scope.
>   * No known symbols currently in scope.
>   * No known symbols declared locally.
> No known possible completions.
> When Semantic cannot find a symbol, it could be because the include
> path was setup incorrectly.
>
>
> Include Path Summary:
>
> This file's project include search is handled by the EDE object:
>    Buffer Target:  #<ede-cpp-root-target /home/zamf/esd/lib/Core/>
>    Buffer Project: #<ede-cpp-root-project esd>
>    Backup Locator: #<ede-locate-base Loc>
>
>
> The system include path is:
>    /usr/include
>    /usr/local/include/
>    /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include/
>    /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include-fixed/
>    /usr/include/
>    /usr/include/c++/4.4/
>    /usr/include/c++/4.4/x86_64-linux-gnu/
>    /usr/include/c++/4.4/backward/
>
>
> Include Summary: /home/zamf/esd/lib/Core/Executor.cpp
>
> Executor.cpp contains 0 includes.
>
>   No unknown includes.
>
>
> This is the project configuration
>
> (ede-cpp-root-project "esd"
>                  :name "esd"
>                  :file "~/esd/Makefile"
>                  :include-path '("/"
>                                  "/include"
>                                  )
>                  :system-include-path '("/usr/include/"
>                                         "~/llvm/llvm-2.6/include")
>                  :spp-table '(("isUnix" . "")
>                               ("BOOST_TEST_DYN_LINK" . "")))
>
> Thanks,
> Cristi
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Cedet-devel mailing list
> Cedet-devel@...
> https://lists.sourceforge.net/lists/listinfo/cedet-devel
>

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Cedet-devel mailing list
Cedet-devel@...
https://lists.sourceforge.net/lists/listinfo/cedet-devel