@title Plans for the future
@link Plans
@license
Copyright (c) 2000, 2001, 2002, 2005, 2006 Tama Communications Corporation
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1
@body
Plans of the highest priority are listed first.
<p>
<ul>
<li>Treat enum members as definitions.(C)
<li>Generate link from 'require', 'require_once' and 'include_once'.(PHP)
<li>Support of PHP language in the following commands in gtags.el.
	<ul>
        <li>gtags-find-tag-by-event
        <li>gtags-find-tag-from-here.
	</ul>
<li>Support glob pattern for path name search (global -P).
<li>Rewrite gtags-parser(1) using flex(1) completely.
<li>Support new languages.
	Here is a list of candidates:
        <ul>
	<li>Lex
	<li>C#
	<li>Scheme
        </ul>
<li>Add support of built-in parser for gtags(1).<br>
	Since this parser is linked to gtags at function layer, we can make
	simpler and more efficient gtags without any external commands.
<li>Rewrite function header using Doxygen style.
<li>The --dynamic option generates not only index files but also hypertext
	of source code itself.
<li>Support gtags-query-replace (gtags.el).
<li>Visual interface using GUI.
<li>Ttags(1) command.<br>
        Ttags(1) is similar to htags(1) but makes TeX source for a book
        instead of hypertext.
<li>Allow spaces in path name of source files.
<li>Support multi-bytes code set.
<li>Make the links in the hypertext generated by htags(1) context sensitive.<br>
	For example, if you have a pointer p to a struct B with a field b,
	and write p->b in the code, the "b" is linked to the field in B.
	It supports struct, class and namespace(C++).
<li>Support tag type. (like Exuberant Ctags.)
<li>Pickup definitions of data type, enum name, enum value,
	union name and struct name. Finally, remove GSYMS. (gtags-parser, gtags)
</ul>
Any contributions are appreciated.
Please see <a href=contribute.html>contribution</a>.