diff options
author | Kristaps Dzonsons <kristaps@bsd.lv> | 2010-06-12 11:41:50 +0000 |
---|---|---|
committer | Kristaps Dzonsons <kristaps@bsd.lv> | 2010-06-12 11:41:50 +0000 |
commit | 16173bda3531a2bb54b45b2e327c8b7e2cf37fd6 (patch) | |
tree | f56dca9a70f2620b119aa051dbc980a7576967bf /mdoc_validate.c | |
parent | dfe0c6ee455f4a355885a711c81c5ae06ac20160 (diff) | |
download | mandoc-16173bda3531a2bb54b45b2e327c8b7e2cf37fd6.tar.gz |
Removed stipulation that an empty `Bd -offset' will default to 6n. Not
sure where this came about. Added regression tests to convince myself
that this is so. Also consolidated COMPATIBILITY notes regarding `Bd'.
Added COMPATIBILITY note to the effect that old groff pukes on `Bd
-compact -ragged' (regression test will fail on old groff).
Diffstat (limited to 'mdoc_validate.c')
-rw-r--r-- | mdoc_validate.c | 19 |
1 files changed, 2 insertions, 17 deletions
diff --git a/mdoc_validate.c b/mdoc_validate.c index 10316fc4..ed0a4c25 100644 --- a/mdoc_validate.c +++ b/mdoc_validate.c @@ -731,23 +731,8 @@ pre_bd(PRE_ARGS) dup = (NULL != n->data.Bd.offs); break; } - /* - * If empty, assign it to a sane default, which - * groff stipulates is about 8n. - */ - /* - * FIXME: remove this. - * - * Where the hell did I get the idea that this - * happens? - */ - assert(1 == n->args->refcnt); - n->args->argv[i].sz++; - n->args->argv[i].value = - mandoc_malloc(sizeof(char *)); - n->args->argv[i].value[0] = - mandoc_strdup("8n"); - offs = n->args->argv[i].value[0]; + if ( ! mdoc_nmsg(mdoc, n, MANDOCERR_IGNARGV)) + return(0); break; case (MDOC_Compact): comp = 1; |