-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ted Gifford skrev 12. mai 2009 21:01:
>> Andrew Gehring wrote:
>>> On Tue, May 12, 2009 at 7:06 AM, jevans  wrote:
>>>> Since line numbers can shift so easily, how about something like:
>>>>  [[Include(source:trunk/somefile.cpp, '// Important section', 20)]]
>>>>
>>>> where the second parameter could be a regex matching something in the
>>>> file.
>>>>
> Why not have a regex for the end line as well?

I believe that is called a "patch"... While a regexp might be easier
sometimes that linenumbers -- I think reffering to trunk wouldn't be a
very good idea -- reffering to an actual version might be better (then
line-numbers would never change).

The "real" problem here is synchronizing documentation in the wiki with
code in the repository -- I'd say either move documentation closer to
the source (same repo, same changeset) -- or keep the documentation in
the wiki do something that's less prone to change -- i.e. API documentation.

I don't have a problem with improvements to the includeplugin to make
all this stuff possible -- just thought it worth pointing out that this
might be solving the right problem in the wrong place...

- -e

- --
 .---.  Eirik Schwenke <[email protected]>
( NSD ) Harald HÃ¥rfagresgate 29            Rom 150
 '---'  N-5007 Bergen            tlf: (555) 889 13

  GPG-key at pgp.mit.edu  Id 0x8AA3392C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoK2DwACgkQxUW7FIqjOSwzaACgr3YEt45ObNwyAHEvUHXgEoLC
eIQAn22rJ1Kp92xkPxgU4mAJuF2HCZlH
=RMH1
-----END PGP SIGNATURE-----

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to