Re: SEarch across files (long & boring for non-programmers)

["..." adpf@xxxxxxxx]

Carl--I inferred from Harry's msg that SSE.PM appends an ascii 13 to the
string in question. Looking at the actual code, I see that XyW3 renders
the char as a cryptic multi-byte--i.e., volatile but always BF--char.
(I've always thought that was ascii 13 was an 8th note but, peering into
my screen, I guess I do discern a double tail.)

≪	A legal func would emphatically *not* be safer for this purpose,
'cause the SEarch string might very well contain a func (vide the recent
discussions here about getting 3-byte funcs on the CMline)!. If I were
doing this in III+, I'd manufacture a weird 3-byter that no one would
ever need to search for, or use a different workaround altogether. ≫

Using a func symbol as the appended char is quite safe in my v3 code in
that I can't think of a situation where I'd be appending the func symbol
to a string that wasn't captured earlier: I can place a func symbol on
the CMline once or even any number in combination, but have never worked
out how to capture them on the fly for later retrieval. Always open to
suggestions. As it is, if I felt a situation made appending a func symbol
risky I'd probably add a test along these lines ...

	{sv14,+X}{sv86,CO }{lb+}{sx12,{is14}+{is86}}{sx13,{is00}+{is12}}
	{if{is12}e{is13}><@siz({is13}-4}{sv86,NO }{gl+}
... and might try other func symbols if necessary before ...
	{ei}{xs13,12,14,12,16}{xs12,86,13,86,14}

								 	--a

============================= adpFisher  nyc