Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!ll-xn!ames!pasteur!ucbvax!decwrl!decvax!mcnc!thorin!unc!alexande
From: alexande@unc.cs.unc.edu (Geoffrey D. Alexander)
Newsgroups: comp.unix.wizards
Subject: Re: Problem with xstr
Summary: I found my own answer
Message-ID: <4323@thorin.cs.unc.edu>
Date: 22 Sep 88 02:39:57 GMT
References: <4252@thorin.cs.unc.edu> <145@taux02.UUCP> <4322@thorin.cs.unc.edu>
Sender: news@thorin.cs.unc.edu
Lines: 9

In article <4322@thorin.cs.unc.edu>, I said:
> 
> I have yet to receive an answer to my question.  Does anyone know how to make
> xstr handle large lines potentially generated by the C preprocessor?

Well, I found the source to xstr.  Simply changing the three occurances of 
BUFSIZ to BUFSIZ*16 fixed my problem.

Geoff Alexander