Thread: Re: [cedet-semantic] newbie help
Brought to you by:
zappo
From: David P. <dav...@wa...> - 2004-06-14 09:44:25
|
Hi Ian, [...] > Eric> If you want to do something other than generate tags, you will > Eric> need to write a grammar that returns what you are looking for. An > Eric> example of what you want to do would help us target suggestions. > > I _expect_ to write a grammar --- I never thought of avoiding it. The > language has a publicly available yacc-like machine readable grammar, > so it shouldn't be a problem at all. But how do I "plug" it in? That is, > what are the details of, quoting you, > > Eric> you probably need to call the lexical analyzer and > Eric> `semantic-parse-stream' or `semantic-parse-region' yourself to > Eric> manage subsets of a buffer. > You can find some documentation in the "Semantic Language Writer's guide: (semantic-langdev).", in chapter "Writing Parsers" section "Parser Backend Support". Particularly, it gives an example of a back end Elisp file (see section "Example Backend File"). You can also use existing back end files in the bovine, or more probably the wisent directories (wisent-java.el, wisent-python.el), as a starting point for your work. Anyway, that point need to be better documented in the manual (perhaps a kind of tutorial would be a good mean to complete the sample back end file?). All we need it more free time (unlikely), or more people who volunteer to help us to improve the documentation ;-) Good luck! David |
From: Berndl, K. <kla...@sd...> - 2004-06-15 08:00:39
|
You should upgrade to the latest cedet-suite, available at http://cedet.sf.net. You are using the old semantic 1.4.X and not the cedet-suite incl. wisent etc... Klaus -----Original Message----- From: ced...@li... To: dav...@wa... Cc: ced...@li... Sent: 6/14/2004 3:57 PM Subject: Re: [cedet-semantic] newbie help David> You can find some documentation in the "Semantic Language David> Writer's guide: (semantic-langdev).", in chapter "Writing David> Parsers" section "Parser Backend Support". Particularly, it David> gives an example of a back end Elisp file (see section "Example David> Backend File"). I see no such document, nor the wisent.* files Eric talks about. Is my distribution shipping an old version of semantic, or worse, have they stripped this essential documentation? Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==============-==============-====================================== ====== ii semantic 1.4.4-5 A lexer, parser-generator, and parser writte Package: semantic Status: install ok installed Priority: optional Section: devel Installed-Size: 1032 Maintainer: Debian QA Group <pac...@qa...> Architecture: all Version: 1.4.4-5 Depends: speedbar | speedbar-beta, emacs21 | xemacs21, eieio (>= 0.17-1) Conffiles: /etc/emacs/site-start.d/50semantic.el 00746dfa7286849647fee103bbf146d6 Description: A lexer, parser-generator, and parser written in elisp The Semantic Bovinator's goal is to provide an intermediate API for authors of language agnostic tools who want to deal with languages in a generic way. It also provides a simple way for Mode Authors, who are experts in their language, to provide a parser for those tool authors, without knowing anything about those tools. . The Semantic Bovinator is made up of these important pieces: - lexer: Converts a language into a token stream - parser: Converts a token stream into a stream of nonterminals defined by the language. - parser-generator: Converts a language definition into a table usable by the parser. (Written using the Semantic Bovinator) - Language Definitions: Parsers already existing for the parser generator language (Bovine Normal Form), Emacs Lisp, and C. - speedbar browser: Code for browsing a generated nonterminal list with Speedbar. - Documentation generator: Identifies inline documentation in source code, and can convert it to texinfo. It can also create inline documentation. -- "It's not true or not." A reality show producer (real quote) ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ cedet-semantic mailing list ced...@li... https://lists.sourceforge.net/lists/listinfo/cedet-semantic |
From: Ian Z. <it...@bu...> - 2004-06-15 14:28:46
|
Klaus> You should upgrade to the latest cedet-suite, available at Klaus> http://cedet.sf.net. You are using the old semantic 1.4.X and not Klaus> the cedet-suite incl. wisent etc... I see. That means I must install a bunch of other stuff which for which I don't have any use (egre, speedbar, ...?) so I'll probably end up rolling my own. Thanks for the help, anyway. -- "It's not true or not." A reality show producer (real quote) |
From: Berndl, K. <kla...@sd...> - 2004-06-15 15:15:57
|
> I see. That means I must install a bunch of other stuff which for which >I don't have any use (egre, speedbar, ...?) so I'll probably end up >rolling my own. Thanks for the help, anyway. I do not want to twist your arm but what are the problems you expect when installing things like cogre or speedbar?? Just download the cedet1.0beta2b.tar.gz tarball, unpack it, go to the new cedet-directory and call "make clean-all; make" from the command line. Then add to your .emacs the line (load-file "/path/to/cedet/common/cedet.el") and Bob will be your uncle - it doesn't matter iof you have use for cogre or speedbar because they will not bother you! They will quietly reside on your disk and they will simple do nothing (if you do not need and use them) Just give it a try.... Klaus -- "It's not true or not." A reality show producer (real quote) |
From: Ian Z. <it...@bu...> - 2004-06-14 13:57:42
|
David> You can find some documentation in the "Semantic Language David> Writer's guide: (semantic-langdev).", in chapter "Writing David> Parsers" section "Parser Backend Support". Particularly, it David> gives an example of a back end Elisp file (see section "Example David> Backend File"). I see no such document, nor the wisent.* files Eric talks about. Is my distribution shipping an old version of semantic, or worse, have they stripped this essential documentation? Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==============-==============-============================================ ii semantic 1.4.4-5 A lexer, parser-generator, and parser writte Package: semantic Status: install ok installed Priority: optional Section: devel Installed-Size: 1032 Maintainer: Debian QA Group <pac...@qa...> Architecture: all Version: 1.4.4-5 Depends: speedbar | speedbar-beta, emacs21 | xemacs21, eieio (>= 0.17-1) Conffiles: /etc/emacs/site-start.d/50semantic.el 00746dfa7286849647fee103bbf146d6 Description: A lexer, parser-generator, and parser written in elisp The Semantic Bovinator's goal is to provide an intermediate API for authors of language agnostic tools who want to deal with languages in a generic way. It also provides a simple way for Mode Authors, who are experts in their language, to provide a parser for those tool authors, without knowing anything about those tools. . The Semantic Bovinator is made up of these important pieces: - lexer: Converts a language into a token stream - parser: Converts a token stream into a stream of nonterminals defined by the language. - parser-generator: Converts a language definition into a table usable by the parser. (Written using the Semantic Bovinator) - Language Definitions: Parsers already existing for the parser generator language (Bovine Normal Form), Emacs Lisp, and C. - speedbar browser: Code for browsing a generated nonterminal list with Speedbar. - Documentation generator: Identifies inline documentation in source code, and can convert it to texinfo. It can also create inline documentation. -- "It's not true or not." A reality show producer (real quote) |