Regress libedit needs header files generated during src libeditbuild. Improve dependencies to resolve this more reliably.requested by claudio@
Implement the generated dependency with a stamp file to avoid needlessrecompiling of the test programs. Add some RCS ids.
Fix building the libedit regress programs.
Generate source and header files for regress on demand.OK espie@
The libedit regress tests require header files generated during thebuild. Add a dependency to run make depend in /usr/src/lib/libedit.Problem found by otto@; OK schwarze@
fix test after the errno reshuffle; ok swarsche@
deal with the el_errno -> read_errno cleanup, read.c rev. 1.43
cope with simplified chared/read interface
adapt to recently changed internal interface of read_getcmd()
cope with the deletion of Char, use wchar_t
drop -DWIDECHAR, it's no longer needed
initialize el_state.metanext before testing read_getcmd()
Fix the CHARSET_IS_UTF8 case in read_char().For now, this mainly help programs explicitly usingwide-character functions like el_wgetc(3) and el_wgets(3).1. After reading an invalid byte sequence,
Fix the CHARSET_IS_UTF8 case in read_char().For now, this mainly help programs explicitly usingwide-character functions like el_wgetc(3) and el_wgets(3).1. After reading an invalid byte sequence, do not throw away additionalvalid bytes; fix by me using mbrtowc(3), obsoleting utf8_islead().2. When read(2) returns EOF, return that information to the caller,do not prod on and potentially access garbage data in the buffer;from Linas Vepstas via NetBSD read.c rev. 1.70 2013/05/27.3. After read__fixio() failure, restore errno to the one set by read();from Steffen Nurpmeso via NetBSD read.c rev. 1.68 2012/09/10.4. After read__fixio() success, restore errno to the initial stateupon function entry; fix by me.OK czarkoff@. Also committed to NetBSD.
show more ...
More unit tests for libedit.Those that still fail are commented out in the Makefiles for now;i have patches for them.
Test the C/POSIX locale too, in addition to UTF-8.
Slowly start a unit test suite for libedit; Christos is right thatfiddling with the internals of that code is dangerous without it.Intentionally not linked to the build yet, because many of the tes
Slowly start a unit test suite for libedit; Christos is right thatfiddling with the internals of that code is dangerous without it.Intentionally not linked to the build yet, because many of the testsstill fail: The related bugfixes are too intrusive right now and willgo in after unlock.