1.\" $NetBSD: vgrindefs.5,v 1.7 2001/12/08 19:23:05 wiz Exp $ 2.\" 3.\" Copyright (c) 1989, 1991, 1993 4.\" The Regents of the University of California. All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by the University of 17.\" California, Berkeley and its contributors. 18.\" 4. Neither the name of the University nor the names of its contributors 19.\" may be used to endorse or promote products derived from this software 20.\" without specific prior written permission. 21.\" 22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 25.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 32.\" SUCH DAMAGE. 33.\" 34.\" @(#)vgrindefs.5 8.1 (Berkeley) 6/6/93 35.\" 36.Dd June 6, 1993 37.Dt VGRINDEFS 5 38.Os 39.Sh NAME 40.Nm vgrindefs 41.Nd language definition data base for 42.Xr vgrind 1 43.Sh SYNOPSIS 44.Nm 45.Sh DESCRIPTION 46The 47.Nm 48file 49contains all language definitions for 50.Xr vgrind 1 . 51The data base is 52very similar to 53.Xr termcap 5 . 54.Sh FIELDS 55The following table names and describes each field. 56.Pp 57.Bl -column Namexxx Tpexxx 58.Sy Name Type Description 59.It "pb str regular expression for start of a procedure" 60.It "bb str regular expression for start of a lexical block" 61.It "be str regular expression for the end of a lexical block" 62.It "cb str regular expression for the start of a comment" 63.It "ce str regular expression for the end of a comment" 64.It "sb str regular expression for the start of a string" 65.It "se str regular expression for the end of a string" 66.It "lb str regular expression for the start of a character constant" 67.It "le str regular expression for the end of a character constant" 68.It "tl bool present means procedures are only defined at the top lexical level" 69.It "oc bool present means upper and lower case are equivalent" 70.It "kw str a list of keywords separated by spaces" 71.El 72.Sh EXAMPLES 73The following entry, which describes the C language, is 74typical of a language entry. 75.Bd -literal 76C|c:\ 77:pb=^\ed?*?\ed?\ep\ed?\e(\ea?\e):bb={:be=}:cb=/*:ce=*/:sb=":se=\ee":\e 78:lb=':le=\ee':tl:\e 79:kw=asm auto break case char continue default do double else enum\e 80extern float for fortran goto if int long register return short\e 81sizeof static struct switch typedef union unsigned while #define\e 82#else #endif #if #ifdef #ifndef #include #undef # define else endif\e 83if ifdef ifndef include undef: 84.Ed 85.Pp 86Note that the first field is just the language name (and any variants 87of it). Thus the C language could be specified to 88.Xr vgrind 1 89as "c" or "C". 90.Pp 91Entries may continue onto multiple lines by giving a \e as the last 92character of a line. 93Capabilities in 94.Nm 95are of two types: 96Boolean capabilities which indicate that the language has 97some particular feature 98and string 99capabilities which give a regular expression or 100keyword list. 101.Sh REGULAR EXPRESSIONS 102.Nm 103uses regular expression which are very similar to those of 104.Xr ex 1 105and 106.Xr lex 1 . 107The characters `^', `$', `:' and `\e' 108are reserved characters and must be 109"quoted" with a preceding 110.Ql \e 111if they 112are to be included as normal characters. 113The metasymbols and their meanings are: 114.Bl -tag -width indent 115.It $ 116the end of a line 117.It \&^ 118the beginning of a line 119.It \ed 120a delimiter (space, tab, newline, start of line) 121.It \ea 122matches any string of symbols (like .* in lex) 123.It \ep 124matches any alphanumeric name. In a procedure definition (pb) the string 125that matches this symbol is used as the procedure name. 126.It () 127grouping 128.It \&| 129alternation 130.It ? 131last item is optional 132.It \ee 133preceding any string means that the string will not match an 134input string if the input string is preceded by an escape character (\e). 135This is typically used for languages (like C) which can include the 136string delimiter in a string by escaping it. 137.El 138.Pp 139Unlike other regular expressions in the system, these match words 140and not characters. Hence something like "(tramp|steamer)flies?" 141would match "tramp", "steamer", "trampflies", or "steamerflies". 142.Sh KEYWORD LIST 143The keyword list is just a list of keywords in the language separated 144by spaces. If the "oc" boolean is specified, indicating that upper 145and lower case are equivalent, then all the keywords should be 146specified in lower case. 147.Sh FILES 148.Bl -tag -width /usr/share/misc/vgrindefs -compact 149.It Pa /usr/share/misc/vgrindefs 150File containing terminal descriptions. 151.El 152.Sh SEE ALSO 153.Xr troff 1 , 154.Xr vgrind 1 155.Sh HISTORY 156The 157.Nm 158file format appeared in 159.Bx 4.2 . 160