I have a wrapper class for the MS Office Products, last time I built it was way back for Office 2000.
I had a set of #imports for that version, but looking in the various directories seem to have changed a bit.
This is what I currently use, has anyone got an updated list for MS Office 2013?
The steps are correct and it worked fine in Office 2000. I had worked on Word automation in C++ / Office 2000 .
Yes, I could reproduce the errors. Probably we need to make some changes, for working on C++ / Office.
Have a look at [^] ; the steps in which the author makes a change to import. Also check the Word automation using C++ [^] - specially the Solution1.h/cpp and Solution1.h/cpp to view how imports are changed.
I wonder what data structure is good for the above logic and application.
The problem in this question is that you didn't actually tell us a lot about the logic and application. You only told us about the scope of input values, and that these values are gathered in batches and processed (filtering out duplicates) before sending out.
You didn't tell us if anything of this is time-critical, or you're working with restricted amounts of memory - should we try to optimize for either?
Also, is it more important for the receiver to receive the data in a timely manner, requiring on-the-fly processing so you can send out the batch right after the end of the cycle - or can you afford to delay the processing until after receiving the last input of the cycle, before sending it out?
The answer to these questions will influence what algorithm to use, and the algorithm will influence what data structures to use.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)