src-test2/usr.bin/sed/process.c, branch release/7.0.0_cvs

This commit was manufactured by cvs2svn to create tag

2008-02-24T05:45:17Z

'RELENG_7_0_0_RELEASE'. This commit was manufactured to restore the state of the 7.0-RELEASE image.

Drop the argument to the OUT macro because it can't emit

2007-06-12T12:17:25Z

anything but the pattern space anyway. Apply style(9) to the macro. Tested with: md5(1)

Don't forget to clear out the hold space for each subsequent file

2007-06-12T12:05:24Z

when in -i mode so that each file gets a clean context of its own. Add a regression test for the bug. Tested with: regression tests

There is a symbolic antonym for REPLACE as a flag to cspace()

2007-06-12T10:56:38Z

and mf_fgets(): APPEND. So use it instead of a 0 constant for clarity. Tested with: md5(1)

Change the semantics of -i (in-place editing) so that it treats

2007-04-21T01:21:36Z

each file independently from other files. The new semantics are desired in the most of practical cases, e.g.: delete lines 5-9 from each file. Keep the previous semantics of -i under a new option, -I, which uses a single continuous address space covering all files to edit in-place -- they are too cool to just drop them. Add regression tests for -i and -I. Approved by: dds Compared with: GNU sed Discussed on: -hackers MFC after: 2 weeks

Don't forget to close the range if we branched over its end

2007-04-02T08:14:46Z

and had no chance to match it by the 2nd address precisely. Otherwise the unclosed range would bogusly extend to the end of stream. Add a basic regression test for the bug fixed. (This change also fixes the more complex case 5.3 from `multitest.t'.) Compared with: SUN and GNU seds Tested by: regression tests MFC after: 1 week

Prevent foot-shooting in advance: Put the MATCH() macro's value

2007-04-02T06:47:48Z

in parentheses. The ?: operator has a remarkably low precedence, so expressions like (MATCH(foo) && bar) would have an unexpected meaning w/o the parentheses around MATCH(). Tested with: md5(1)

This trivial change should fix at least 3 similar bugs. All of

2007-04-01T13:25:03Z

them are related to the `c' function's need to know if we are at the actual end of the address range. (It must print the text not earlier than the whole pattern space was deleted.) It appears the only sed function with this requirement. There is `lastaddr' set by applies(), which is to notify the `c' function, but it can't always help because it's false when we are hitting the end of file early. There is also a bug in applies() due to which `lastaddr' isn't set to true on degenerate ranges such as `$,$' or `N,$' if N appears the last line number. Handling early EOF condition in applies() could look more logical, but it would effectively revert sed to the unreasonable behaviour rev. 1.26 of main.c fought against, as it would require lastline() be called for each line within each address range. So it's better to call lastline() only if needed by the `c' function. Together with this change to sed go regression tests for the bugs fixed (c1-c3). A basic test of `c' (c0) is also added as it helped me to spot my own error. Discussed with: dds Tested by: the regression tests MFC after: 1 week

Make the comment for cspace() match reality.

2007-03-31T09:08:22Z

Fix using "P" command on empty pattern space. If the "P" command is

2006-05-27T19:32:28Z

used once on a non-empty pattern space and then again on an empty pattern space, the second usage restores the pattern space length to the length that it had when the first "P" was used. PR: bin/96052 Submitted by: Andrey Zholos MFC after: 7 days