Looks cool, although I can notice a few possible improvements (in addition to removing the dependence on counting next 7 chars). Thanks for the obvious effort. :-) Mine is at http://dotnetdevelopment.pastebin.com/f6ccabd5d
My version doesn't write out the file yet, because I couldn't quite figure out what to do when the items retrieved from both files have differing counts. On Oct 21, 10:49 am, Processor Devil <[email protected]> wrote: > http://dotnetdevelopment.pastebin.com/m6ee056a3<http://dotnetdevelopment.pastebin.com/m6ee056a3>Here > you are :). > It is made for my usage, so sorry for hard typing the file locations. > > 2009/10/20 Cerebrus <[email protected]> > > > > > > > Ah yes, now that you mention it, it does look like that (I didn't > > bother to count the chars). Nevertheless, it might help not to rely on > > a hard coded count. > > > Notwithstanding the count issue, your suggested logic seems to be the > > synchronous reading of both input files as well as writing to the > > output file (which is a very interesting method)... I hadn't thought > > of that. I'd like to see an elaborated version of your statement, > > please. My version was more akin to reading each file one by one and > > writing in the same sequential manner. > > > On Oct 20, 9:25 pm, Processor Devil <[email protected]> wrote: > > > Hi Cerebrus, > > > it looks like data are always of the same length... > > > so it should be enough to just read 7 chars from file (aaaaaaa), 7 chars > > > from the other file, write it both to another file and repeat...- Hide > > > quoted text - > > - Show quoted text -
