StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>It's the number of bytes of tag data following the newline after the number.</p> <p>Edit: It also doesn't include the ^L character between file tag data. Remember etags comes from a time long ago where reading a 500KB file was an expensive operation. ;)</p> <p>Here's a complete tags file. I'm showing it two ways, the first with control characters as ^X and no invisible characters. The end-of-line characters implicit in your example are ^J here:</p> <pre><code>^L^J hello.cc,45^J int main(^?5,41^J int foo(^?9,92^J int bar(^?13,121^J ^L^J hello.h,15^J #define X ^?2,1^J </code></pre> <p>Here's the same file displayed in hex:</p> <pre><code>0000000 0c 0a 68 65 6c 6c 6f 2e 63 63 2c 34 35 0a 69 6e ff nl h e l l o . c c , 4 5 nl i n 0000020 74 20 6d 61 69 6e 28 7f 35 2c 34 31 0a 69 6e 74 t sp m a i n ( del 5 , 4 1 nl i n t 0000040 20 66 6f 6f 28 7f 39 2c 39 32 0a 69 6e 74 20 62 sp f o o ( del 9 , 9 2 nl i n t sp b 0000060 61 72 28 7f 31 33 2c 31 32 31 0a 0c 0a 68 65 6c a r ( del 1 3 , 1 2 1 nl ff nl h e l 0000100 6c 6f 2e 68 2c 31 35 0a 23 64 65 66 69 6e 65 20 l o . h , 1 5 nl # d e f i n e sp 0000120 58 20 7f 32 2c 31 0a X sp del 2 , 1 nl </code></pre> <p>There are two sets of tag data in this example: 45 bytes of data for hello.cc and 15 bytes for hello.h.</p> <p>The hello.cc data starts on the line following "hello.cc,45^J" and runs for 45 bytes--this also happens to be complete lines. The reason why bytes are given is so code reading the file can just allocate room for a 45 byte string and read 45 bytes. The "^L^J" line is after the 45 bytes of tag data. You use this as a marker that there are more files remaining and also to verify that the file is properly formatted.</p> <p>The hello.h data starts on the line following "hello.h,15^J" and runs for 15 bytes.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload