lean2/tests/lean/interactive/in4.input.expected.out

26 lines
342 B
Text
Raw Normal View History

-- BEGINWAIT
-- ENDWAIT
-- BEGININFO
-- TYPE|9|0
eq (tst.foo a b) (tst.foo a b)
-- ACK
-- IDENTIFIER|9|0
rfl
-- ACK
-- ENDINFO
-- AFTER REMOVE 8&9
-- BEGININFO STALE NAY
-- ENDINFO
refactor(frontends/lean/scanner): remove dependency to seekg and unget methods It is not safe to use seekg for textual files. Here is a fragment from a C++ manual: seekg() and seekp() This pair of functions serve respectively to change the position of stream pointers get and put. Both functions are overloaded with two different prototypes: seekg ( pos_type position ); seekp ( pos_type position ); Using this prototype the stream pointer is changed to an absolute position from the beginning of the file. The type required is the same as that returned by functions tellg and tellp. seekg ( off_type offset, seekdir direction ); seekp ( off_type offset, seekdir direction ); Using this prototype, an offset from a concrete point determined by parameter direction can be specified. It can be: ios::beg offset specified from the beginning of the stream ios::cur offset specified from the current position of the stream pointer ios::end offset specified from the end of the stream The values of both stream pointers get and put are counted in different ways for text files than for binary files, since in text mode files some modifications to the appearance of some special characters can occur. For that reason it is advisable to use only the first prototype of seekg and seekp with files opened in text mode and always use non-modified values returned by tellg or tellp. With binary files, you can freely use all the implementations for these functions. They should not have any unexpected behavior.
2014-09-18 22:24:48 +00:00
-- BEGININFO STALE NAY
-- ENDINFO
-- BEGINWAIT
-- ENDWAIT
-- BEGININFO
-- TYPE|9|0
eq (tst.foo a b) (tst.foo a b)
-- ACK
-- IDENTIFIER|9|0
rfl
-- ACK
-- ENDINFO