🚀 go-pugleaf

So far, I have used BC++ for about three hours.
In that time, I have noticed that the environment is MUCH
more stable than TC++ 1.00/1.01.. *no* crashes of any kind.
I have yet to try the WINDOWS3 stuff, though.

HOWEVER.. the following two bugs may be of general interest.
I will likely call Borland about them after the Easter weekend.


	1) The <conio.h> routines are slightly broken.
	When outputing a "\r\n" sequence using either putch()
	or cputs(), these routines no longer perform an implicit
	clreol() to clean the rest of the line before advancing.
	This broke my port of LESS.. very obvious, as the screen
	just filled up with identical "garbage" at the end of all
	short lines of output.

	My interim work-a-round is to simply perform a clreol()
	immediately before outputing "\r\n".

	2) The GREP.COM program *still* does not know how to display
	its permanent option settings correctly.  Try doing GREP -o -u
	and then GREP ? to see what I mean.  This bug has been there
	from TC++ 1.00 onwards.  To fix it in BC++ 2.00, apply the 
	following patch to GREP.COM (note also that even though the
	GREP.COM is not identical to previous releases, it still has
	the same version number, 3.0.  haha!):

	For the GREP.COM that comes with BC++ 2.00,
	At offset $1A83, the values:  8C 19 A9 19 BD
	should be changed to:         A9 19 BD 19 8C

	For the older version of this from TC++ 1.00,
	At offset $1A89, the values:  92 19 AF 19 C3
	should be changed to:         AF 19 C3 19 92

Enjoy.
---
MLORD@BNR.CA  Ottawa, Ontario *** Personal views only ***
begin 644 NOTSHARE.COM ; Free MS-DOS utility - use instead of SHARE.EXE
MZQ.0@/P/=`J`_!9T!2[_+H``L/_/+HX&+`"T2<TAO@,!OX0`N1(`C,B.P/.DS
<^K@A-<TAB1Z``(P&@@"ZA`"X(27-(?NZE@#-)P#-5
``
end