On 3/15/2023 1:28 AM, Rob van der Heij wrote:
> Splitting a record with no words will pass the record (see example in usage
> note :-)
Right, and in that case it was a real null line in the input ...0a0a...,
so it hasn't added any *extra* null records.
¬R
On 3/15/2023 10:49 AM, John P. Hartmann wrote:
> If we are speaking two records, wouldn't SPEC be able to do what you want?
Yes, since the lists are joined into single records, I was able to use
SPECS to swap the order and then CHOP|SPLIT|JUXTAPOSE to split up the
lists and juxtapose each item wit
On 3/13/2023 7:41 PM, Paul Gilmartin wrote:
> The problem is not well-posed. Consider
> Foo
>
>
> Bar
> Is that two records, or three with a null record between the and
> the .
Figuring out the reasonable assumptions to make to make that decision is
the biggest part of what I m
On Thu, 16 Mar 2023 at 21:29, Glenn Knickerbocker wrote:
> Figuring out the reasonable assumptions to make to make that decision is
> the biggest part of what I meant by "getting it right."
>
Yes, I think we all realized the ambiguity. I was considering these
alternatives (with preference for th
On Thu, 16 Mar 2023 at 21:29, Glenn Knickerbocker wrote:
> I was really thinking of the more general case where the list is already
> in separate records to start with. I guess the thing to do would be to
> inject a null record into the list after each container record, and use
> BUFFER 1 to bu
On 3/16/23 14:46:04, Rob van der Heij wrote:
...
Yes, I think we all realized the ambiguity. I was considering these
alternatives (with preference for the first one)
- line end is any unique sequence of the specified characters, so if you
specify the CR and LF as candidate, then CR, LF, CR L
On 3/16/2023 4:55 PM, Rob van der Heij wrote:
> I guess that's why you don't want to process the entire thing backwards,
You know, I never even thought of that. As long as I can buffer the
whole file, that's certainly straightforward!
In this case, I also want the list items at the front of the
On Thu, 16 Mar 2023 at 22:33, Paul Gilmartin wrote:
>
> Otherwise, the format of the record separator might be an optional
> parameter to your program.
>
We already have the ability to specify the line-end character or string.
The discussion was about when you don't know in advance what convent
On 3/16/2023 4:46 PM, Rob van der Heij wrote:
> alternatives (with preference for the first one)
> - line end is any unique sequence of the specified characters, so if you
> specify the CR and LF as candidate, then CR, LF, CR LF, and LF CR are all
> one single end of line, but CR CR would imply a n
On Thu, 16 Mar 2023 at 23:29, Glenn Knickerbocker wrote:
> On 3/16/2023 4:46 PM, Rob van der Heij wrote:
> > alternatives (with preference for the first one)
> > - line end is any unique sequence of the specified characters, so if you
> > specify the CR and LF as candidate, then CR, LF, CR LF, an
On 3/16/2023 6:38 PM, Rob van der Heij wrote:
> KEEP to include the line end characters in the output stream? Would you
> also need a BEFORE and AFTER, or is it good enough to just have them at the
> end? You could use STRIP TRAILING ANYOF with the same set.
I picture wanting them at the end of th
11 matches
Mail list logo
