I need a program called "FindLine"

[learn64bit]

I think we should use multiThreading in deleteDupliLine app.
otherwise it will take 87 hours...
87 hours is too long for most people.
maybe 30 mins is ok

what I gonna do it
  inputFile
    f.txt
  outputFiles
    g.txt
      all dupliLines goes
    h.txt
      all nonDupliLines goes
(it will let the result can be verified easily by people, then "copy /b" on g.txt and h.txt to get i.txt for deleteEmptyFolder app)

[learn64bit]

deleteDupliLineV422
(.exe only, 1+5 threads)

[learn64bit]

new problem.
we should deleteParentIfChildNotExist.
hope third party app can do it

[jj2007]

If I had a buck$ for every incomprehensible question ever posted, I would own 2 Cadillacs, a house on the Riviera and at least 2 Lear jets.

Wow, I can't believe this nonsense thread is that old

[learn64bit]

(no g.txt and h.txt)it's too complicated. maybe we just simply feed f.txt to deleteFolder

[NoCforMe]

This guy (yes, you, "learn64bit") just keeps plowing ahead like some mindless bulldozer scraping over the same ground again and again. "a.txt", "b.txt", "c.txt" ... no doubt to extend to "x.txt", "y.txt" and "z.txt". No explanation, none, of what these files are, what they do, what their purpose or format is. Plus no explanation, none, of what the code does and what its purpose is. And of course well-meaning but gullible members are getting sucked into this gigantic whirlpool as well.

More popcorn!

[learn64bit]

deleteEmptyFolderV427
(input file is f.txt)
(.exe only)

[learn64bit]

Neither one of those look like

10 seconds

. 

Selective quoting? I actually said

about 10 seconds

Looks like the latest version V360 is slower for you, sinsi?

Sorry, wrong way around 

Previous version
The current time is: 18:05:34.97
The current time is: 18:05:47.84
around 12 seconds

Latest version
The current time is: 18:04:13.45
The current time is: 18:04:19.22
around 6 seconds

Of course that assumes that the results are valid

90% of people think it's valid. because c+d=a.
after I finish the deleteFile app, the result can be verified.
I know I'm later, because I took different way to verify it.
(what am I thinking? it's for fun! haha)

[sudoku]

Since there is no code in your fastest program to check the results for validity, it is normal for people to question the validity of the results.

You said the slowest code took 87 hours  to finish. Now on sinsis computer, presumably the same functions (but faster code) took mere seconds.
On my computer a few minutes.

Just because someone 'thinks' it is valid is not enough, results must be verified. Especially since it is much, much faster than the original.  (87 hours -> 10 seconds)... sheesh.
This is the short explanation. Would be pages, for the longer version. But my time is limited.

I have truncated the post to the bare essence of what was originally posted here, for brevity.

[learn64bit]

deleteFilesV430
(inputfile is e.txt)
(.exe only)

[learn64bit]

yeee hooo! finally I can answer the question.
sinsi's c.txt and d.txt are valid.
the result files have be verified.

now we can try other ideas to speedup the findLine app

[learn64bit]

q: how you verify the result?
a: verified existing files