Hi,

On 2015-02-14 12:13:32, Nicholas Boel wrote to Wilfred van Velzen:
  about: "Re: htick":

 WV>> If both the filename, and the .tic file contained the comma, it's not
 WV>> a htick issue.

 NB> It didn't. The filename was correct, with a period. The comma was only in
 NB> the "replaces" line in the .TIC.

I red over the 'replaces' part. ;)

 NB>>> What I would like to know is if there is a
"normal" way to handle
 NB>>> this? Does htick skip the typo, which in turn would *not* use
 NB>>> that "replaces" command, and continue processing
it successfully
 NB>>> and pass it on to downlinks with the same typo in the .tic? This
 NB>>> seems to be what occurred, and that doesn't seem like a good
 NB>>> idea, IMO.

 WV>> This depends on my remark above...

 NB> Why not just answer it assuming either way instead of stopping on one
 NB> assumption, which wasn't the correct one anyways?

Ok, my opinion:

The processor can't know it's a typo. It can only see that the file to be
replaced doesn't exist on the receiving system. That's a legitimate (local)
situation and not an error in itself.

So the file + .tic can be passed on to the next system.

That the file already exists on the receiving system, and is not replaced
by the replace command, is a local problem, and is dealt with by the local
configuration. It can replace it anyway, it can rename 1 of the 2 files, it
can put the new file in a bad area, etc...

Bye, Wilfred.


--- FMail-W32-1.69.1.95-B20140716