Re: parsing columns

From: offer.kaye@xxxxxxxxx (Offer Kaye)
Date: Thu, 18 Aug 2005 22:33:00 +0300

On 8/18/05, Wiggins d'Anconia wrote:
>
> Though in that case I guess you might be able to determine that it is
> column two because there aren't two spaces,

Alas, were it that simple... :( An extra space will not be included,
even if the l3dat2 would actually have been l3dat3...

> but that is still using the
> assumption that there *must* be at least one space character delimiting
> columns.

1. There *must* be at least one space character between columns.
2. Data is guaranteed not to include a whitespace.

Regards,
--
Offer Kaye
.

References:
- parsing columns
  - From: Offer Kaye
- Re: parsing columns
  - From: Manav Mathur
- Re: parsing columns
  - From: Marcello
- Re: parsing columns
  - From: Wiggins d'Anconia

Prev by Date: Re: Memory Testing
Next by Date: Use of uninitialized value in string at ... ??
Previous by thread: Re: parsing columns
Next by thread: Re: parsing columns
Index(es):
- Date
- Thread

Relevant Pages

Re: removing a space from starting of the text
... Assuming these are numbers, so contain no other spaces, just use Edit/Replace ... and replace the space character with "nothing" (leave the Replace With box ... >cannot do any calculation because of that space. ... Prev by Date: ...
(microsoft.public.excel.worksheet.functions)
Re: Use of s versus space character
... >>> string vs using a space character. ... Xho ... Prev by Date: ...
(comp.lang.perl.misc)
Re: Ubundu: Doing something security-wise with its partition?
... Peter Breuer is presumably referring to the space character you have ... Prev by Date: ...
(comp.os.linux.misc)
Re: Use of s versus space character
... > string vs using a space character. ... Bernard ... Prev by Date: ...
(comp.lang.perl.misc)