In <[EMAIL PROTECTED]>, Andrey A. Chernov wrote:
> On Fri, Jul 28, 2000 at 09:03:49AM +0200, Martin Cracauer wrote:
> > 1) It seems that you can work around the coredump by looking at the
> > next char after \202. For real expansions of variables in
> > here-documents that is \201. Once can probably determine all
> > possible legal combinations and ignore others. However, that
>
> The problem is that all combinations are legal, there can be binary data passed.
> It means that all control chars must be double-escaped first just after data
> reading.
Exactly. When I'm going to fix it, I will use the other solution (char*
-> int* for internal parsed buffers).
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/
BSD User Group Hamburg, Germany http://www.bsdhh.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
