From: ted <thilts@help-for-you.com>
To: xen-devel@lists.xensource.com
Subject: lxr.xensource.com-lxr
Date: Fri, 01 Apr 2005 09:07:13 -0700 [thread overview]
Message-ID: <424D71B1.2000907@help-for-you.com> (raw)
Re: http://lxr.xensource.com/lxr/
This index to Xen source code was apparently loaded into a general
hypertext cross-referencing tool. This tool was apparently written in perl..
" The Linux Cross-Reference project is the testbed application of a
general hypertext cross-referencing tool. (Or the other way around.)
The main goal of the project is to create a versatile cross-referencing
tool for relatively large code repositories. The project is based on
stock web technology, so the codeview client may be chosen from the full
range of available web browsers. On the server side, any Unix-based web
server with cgi-script capability should do nicely.'
Some "reservations" were expressed by the authors regarding the display
of "source code".
I notice the entire source code is numbered and one can reference that
code by number and module being extensively cross-referenced. What
exactly are the "reservations" expressed -- something to do with "sloppy
labelling" being less than a "full code parser".
Do the Xen developers make frequent use of this cross reference tool?
Where would I obtain the perl code for this general hypertext
cross-referencing tool?
Would it not be possible to create a hierarchical tree structure of Xen
by parsing this display presented by the general hypertext
cross-referencing tool???
Thanks -- Ted
next reply other threads:[~2005-04-01 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 16:07 ted [this message]
2005-04-01 21:14 ` lxr.xensource.com-lxr James Bulpin
2005-04-01 22:07 ` lxr.xensource.com-lxr Ted Hilts
2005-04-01 22:52 ` lxr.xensource.com-lxr James Bulpin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=424D71B1.2000907@help-for-you.com \
--to=thilts@help-for-you.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.