| [Top] | [Contents] | [Index] | [ ? ] |
You can browse C++ class hierarchies from within Emacs by using Ebrowse.
1. Introduction What is it and now does it work? 2. Processing Source Files How to process C++ source files 3. Starting to Browse How to start browsing 4. Tree Buffers Traversing class hierarchies 5. Member Buffers Looking at member information 6. Tags-like Functions Finding members from source files Concept Index An entry for each concept defined
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
When working in software projects using C++, I frequently missed software support for two things:
greping through dozens or even hundreds of files.
The design of Ebrowse reflects these two needs.
How does it work?
A fast parser written in C is used to process C++ source files. The parser generates a data base containing information about classes, members, global functions, defines, types etc. found in the sources.
The second part of Ebrowse is a Lisp program. This program reads the data base generated by the parser. It displays its contents in various forms and allows you to perform operations on it, or do something with the help of the knowledge contained in the data base.
Navigational use of Ebrowse is centered around two types of buffers which define their own major modes:
Tree buffers are used to view class hierarchies in tree form. They allow you to quickly find classes, find or view class declarations, perform operations like query replace on sets of your source files, and finally tree buffers are used to produce the second buffer form--member buffers. See section 4. Tree Buffers.
Members are displayed in member buffers. Ebrowse distinguishes between six different types of members; each type is displayed as a member list of its own:
enums, and typedefs defined with class
scope).You can switch member buffers from one list to another, or to another class. You can include inherited members in the display, you can set filters that remove categories of members from the display, and most importantly you can find or view member declarations and definitions with a keystroke. See section 5. Member Buffers.
These two buffer types and the commands they provide support the navigational use of the browser. The second form resembles Emacs' Tags package for C and other procedural languages. Ebrowse's commands of this type are not confined to special buffers; they are most often used while you are editing your source code.
To list just a subset of what you can use the Tags part of Ebrowse for:
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Before you can start browsing a class hierarchy, you must run the parser
ebrowse on your source files in order to generate a Lisp data
base describing your program.
The operation of ebrowse can be tailored with command line
options. Under normal circumstances it suffices to let the parser use
its default settings. If you want to do that, call it with a command
line like:
ebrowse *.h *.cc |
or, if your shell doesn't allow all the file names to be specified on the command line,
ebrowse --files=file |
where file contains the names of the files to be parsed, one per line.
When invoked with option `--help', ebrowse prints a list of
available command line options.
2.1 Specifying Input Files Specifying which files to parse 2.2 Changing the Output File Name Changing the output file name 2.3 Structs and Unions Omitting structs andunions2.4 Regular Expressions Setting regular expression lengths 2.5 Verbose Mode Getting feedback for lengthy operations
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ebrowse to parse
that file.
ebrowse finds no file names on the command line, and no
`--file' option is specified, it reads file names from standard
input. This is sometimes convenient when ebrowse is used as part
of a command pipe.
It is generally a good idea to specify input files so that header files are parsed before source files. This facilitates the parser's work of properly identifying friend functions of a class.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ebrowse to generate a Lisp data base with
name file. By default, the data base is named `BROWSE', and
is written in the directory in which ebrowse is invoked.
If you regularly use data base names different from the default, you might want to add this to your init file:
(add-to-list 'auto-mode-alist '(NAME . ebrowse-tree-mode)) |
where NAME is the Lisp data base name you are using.
ebrowse erases the old contents of the
output file when writing to it. You can instruct ebrowse to
append its output to an existing file produced by ebrowse
with this command line option.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
struct or union in the output.
This is mainly useful when you are converting an existing C program to C++, and do not want to see the old C structs in a class tree.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The parser ebrowse normally writes regular expressions to its
output file that help the Lisp part of Ebrowse to find functions,
variables etc. in their source files.
You can instruct ebrowse to omit these regular expressions by
calling it with the command line switch `--no-regexps'.
When you do this, the Lisp part of Ebrowse tries to guess, from member or class names, suitable regular expressions to locate that class or member in source files. This works fine in most cases, but the automatic generation of regular expressions can be too weak if unusual coding styles are used.
ebrowse.
The smaller the minimum length, the higher the probability that Ebrowse will find a wrong match. The larger the value, the larger the output file and therefore the memory consumption once the file is read from Emacs.
ebrowse.
The larger the maximum length, the higher the probability that the browser will find a correct match, but the larger the value the larger the output file and therefore the memory consumption once the data is read. As a second effect, the larger the regular expression, the higher the probability that it will no longer match after editing the file.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ebrowse prints
a period for each file parsed, and it displays a `+' for each
class written to the output file.
ebrowse print out the names of the files and
the names of the classes seen.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You start browsing a class hierarchy parsed by ebrowse by just
finding the `BROWSE' file with C-x C-f.
An example of a tree buffer display is shown below.
| Collection | IndexedCollection | Array | FixedArray | Set | Dictionary |
When you run Emacs on a display which supports colors and the mouse, you will notice that certain areas in the tree buffer are highlighted when you move the mouse over them. This highlight marks mouse-sensitive regions in the buffer. Please notice the help strings in the echo area when the mouse moves over a sensitive region.
A click with Mouse-3 on a mouse-sensitive region opens a context menu. In addition to this, each buffer also has a buffer-specific menu that is opened with a click with Mouse-3 somewhere in the buffer where no highlight is displayed.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Class trees are displayed in tree buffers which install their own major mode. Most Emacs keys work in tree buffers in the usual way, e.g. you can move around in the buffer with the usual C-f, C-v etc., or you can search with C-s.
Tree-specific commands are bound to simple keystrokes, similar to
Gnus. You can take a look at the key bindings by entering
? which calls M-x describe-mode in both tree and member
buffers.
4.1 Viewing and Finding Class Declarations Viewing and finding a class declaration 4.2 Displaying Members Showing members, switching to member buffers 4.3 Finding a Class Finding a class 4.4 Burying a Tree Buffer Discarding and burying the tree buffer 4.5 Displaying File Names Showing file names in the tree 4.6 Expanding and Collapsing a Tree Expanding and collapsing branches 4.7 Changing the Tree Indentation Changing the tree indentation 4.8 Removing Classes from the Tree Removing class from the tree 4.9 Saving a Tree Saving a modified tree
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can view or find a class declaration when the cursor is on a class name.
The same functionality is available from the menu opened with Mouse-3 on the class name.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Ebrowse distinguishes six different kinds of members, each of which is displayed as a separate member list: instance variables, instance functions, static variables, static functions, friend functions, and types.
Each of these lists can be displayed in a member buffer with a command starting with L when the cursor is on a class name. By default, there is only one member buffer named *Members* that is reused each time you display a member list--this has proven to be more practical than to clutter up the buffer list with dozens of member buffers.
If you want to display more than one member list at a time you can freeze its member buffer. Freezing a member buffer prevents it from being overwritten the next time you display a member list. You can toggle this buffer status at any time.
Every member list display command in the tree buffer can be used with a prefix argument (C-u). Without a prefix argument, the command will pop to a member buffer displaying the member list. With prefix argument, the member buffer will additionally be frozen.
These lists are also available from the class' context menu invoked with Mouse-3 on the class name.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If the branch of the class tree containing the class searched for is currently collapsed, the class itself and all its base classes are recursively made visible. (See also 4.6 Expanding and Collapsing a Tree.)
This function is also available from the tree buffer's context menu.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This command is also provided in the tree buffer's context menu.
Here is an example of a tree buffer with file names displayed.
| Collection (unknown) | IndexedCollection (indexedcltn.h) | Array (array.h) | FixedArray (fixedarray.h) | Set (set.h) | Dictionary (dict.h) |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can expand and collapse parts of a tree to reduce the complexity of large class hierarchies. Expanding or collapsing branches of a tree has no impact on the functionality of other commands, like /. (See also 4.3 Finding a Class.)
Collapsed branches are indicated with an ellipsis following the class name like in the example below.
| Collection | IndexedCollection... | Set | Dictionary |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Classes can be marked for operations similar to the standard Emacs commands M-x tags-search and M-x tags-query-replace (see also See section 6. Tags-like Functions.)
Marked classes are displayed with an > in column one of the tree
display, like in the following example
|> Collection | IndexedCollection... |> Set | Dictionary |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Member buffers are used to operate on lists of members of a class. Ebrowse distinguishes six kinds of lists:
enums and typedefs defined with class scope.
Nested classes will be shown in the class tree like normal classes.
Like tree buffers, member buffers install their own major mode. Also like in tree buffers, menus are provided for certain areas in the buffer: members, classes, and the buffer itself.
5.1 Switching Member Lists Choosing which members to display 5.2 Finding and Viewing Member Source Modifying source code 5.3 Display of Inherited Members 5.4 Searching Members Finding members in member buffer 5.5 Switching to Tree Buffer Going back to the tree buffer 5.6 Filters Selective member display 5.7 Displaying Member Attributes Display of virtualetc.5.8 Long and Short Member Display Comprehensive and verbose display 5.9 Display of Regular Expressions Showing matching regular expressions 5.10 Displaying Another Class Displaying another class 5.11 Burying a Member Buffer Getting rid of the member buffer 5.12 Setting the Column Width Display style 5.13 Forced Redisplay Redrawing the member list
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Both commands cycle through the member list.
Most of the commands are also available from the member buffer's context menu.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can install a hook function to perform actions after a member or class declaration or definition has been found, or when it is not found.
All the commands described above can also be found in the context menu displayed when clicking Mouse-2 on a member name.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
With a prefix argument (C-u), all members in the class tree, i.e. all members the browser knows about appear in the completion list. The member display will be switched to the class and member list containing the member.
Look into the buffer's context menu for a convenient way to do this with a mouse.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
public members. The
`a' stands for `access'.
protected members.
private members.
virtual members.
inline members.
const members.
These commands are also found in the buffer's context menu.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The nine member attributes Ebrowse knows about are displayed as a list a single-characters flags enclosed in angle brackets in front the of the member's name. A `-' at a given position means that the attribute is false. The list of attributes from left to right is
extern "C".
virtual.
inline.
const.
mutable.
explicit.
This command is also in the buffer's context menu.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| isEmpty contains hasMember create | storeSize hash isEqual restoreGuts | saveGuts |
The long display shows one member per line with member name and regular expressions matching the member (if known):
| isEmpty Bool isEmpty () const... | hash unsigned hash () const... | isEqual int isEqual (... |
Regular expressions will only be displayed when the Lisp database has
not been produced with the ebrowse option `--no-regexps'.
See section Regular Expressions.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Regular expressions will only be displayed when the Lisp database has
not been produced with the ebrowse option `--no-regexps',
see Regular Expressions.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
describe-mode.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Ebrowse provides tags functions similar to those of the standard Emacs Tags facility, but better suited to the needs of C++ programmers.
6.1 Finding and Viewing Members Going to a member declaration/definition 6.2 The Position Stack Moving to previous locations 6.3 Searching and Replacing Searching and replacing over class tree files 6.4 Members in Files Listing all members in a given file 6.5 Member Apropos Listing members matching a regular expression 6.6 Symbol Completion Completing names while editing 6.7 Quick Member Display Quickly display a member buffer for some identifier
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The functions in this section are similar to those described in 4.1 Viewing and Finding Class Declarations, and also in 5.2 Finding and Viewing Member Source, except that they work in a C++ source buffer, not in member and tree buffers created by Ebrowse.
If more than one class contains a member with the given name you can select the class with completion. If there is a scope declaration in front of the member name, this class name is used as initial input for the completion.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
When jumping to a member declaration or definition with one of Ebrowse's commands, the position from where you performed the jump and the position where you jumped to are recorded in a position stack. There are several ways in which you can quickly move to positions in the stack:
The stack is not popped, i.e. you can always switch back and forth between positions in the stack. To avoid letting the stack grow to infinite size there is a maximum number of positions defined. When this number is reached, older positions are discarded when new positions are pushed on the stack.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Ebrowse allows you to perform operations on all or a subset of the files mentioned in a class tree. When you invoke one of the following functions and more than one class tree is loaded, you must choose a class tree to use from an electric tree menu. If the selected tree contains marked classes, the following commands operate on the files mentioned in the marked classes only. Otherwise all files in the class tree are used.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The command C-c b l, lists all members in a given file. The file name is read from the minibuffer with completion.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The command C-c b a can be used to display all members matching a given regular expression. This command can be very useful if you remember only part of a member name, and not its beginning.
A special buffer is popped up containing all identifiers matching the regular expression, and what kind of symbol it is (e.g. a member function, or a type). You can then switch to this buffer, and use the command C-c b f, for example, to jump to a specific member.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The command C-c b TAB completes the symbol in front of point.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can quickly display a member buffer containing the member the cursor in on with the command C-c b m.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| Jump to: | *
-
A B C D E F H I K L M N O P R S T U V |
|---|
| Jump to: | *
-
A B C D E F H I K L M N O P R S T U V |
|---|
| [Top] | [Contents] | [Index] | [ ? ] |
| [Top] | [Contents] | [Index] | [ ? ] |
1. Introduction
2. Processing Source Files
3. Starting to Browse
4. Tree Buffers
5. Member Buffers
6. Tags-like Functions
Concept Index
| [Top] | [Contents] | [Index] | [ ? ] |
| Button | Name | Go to | From 1.2.3 go to |
|---|---|---|---|
| [ < ] | Back | previous section in reading order | 1.2.2 |
| [ > ] | Forward | next section in reading order | 1.2.4 |
| [ << ] | FastBack | previous or up-and-previous section | 1.1 |
| [ Up ] | Up | up section | 1.2 |
| [ >> ] | FastForward | next or up-and-next section | 1.3 |
| [Top] | Top | cover (top) of document | |
| [Contents] | Contents | table of contents | |
| [Index] | Index | concept index | |
| [ ? ] | About | this page |