"API" <ari.pikivirta@kolumbus.fi> wrote in message
news:485d909d@newsgroups.borland.com...
> Sure it's wrong, but removing fetch will not break
> the start and end positions because they don't exist
> there in case of bad clients.
Consider good clients that do not use quotes because there are no embedded
spaces. That would be valid syntax, and thus removing the Fetch() would
break those clients that do include the begin/end positions. So again, I
cannot agree with removing the Fetch(). The only possible way that could
work for all situations would be if the code is updated to look for 1-2
trailing numbers at the end of the line. If present, the filename would be
all of the text between the leading commmd and the trailing numbers. Quotes
could then be removed from that remaining text if present.
> Bad clients in most cases doesn't have " marks even
But good clients may not, either.
> so all it has is filename with or without spaces and this
> definetely will work for both good and bad clients now.
No, it would not work in all situations.
Gambit
