[Quickfix-developers] FileLog.cpp question (sorta)
Brought to you by:
orenmnero
From: Bud G. <bud...@ya...> - 2003-05-15 04:51:50
|
Hi Oren and All, I was looking through FileStore.cpp and it seems that there's a problem where the constructor is checking to see if the outgoing and event streams have been successfully opened. The code actually checks to see if the m_incoming stream was successfully opened instead of the outgoing or event log streams. A very minor issue, but the reason I was looking at the code was because I use tail with the -f option on Solaris to see what's going on while debugging or for certification with other parties and the output seems to be delayed longer than the 10 seconds or so I think tail pauses between read attempts. Maybe I'm confused, but I thought std::endl was supposed to flush output in addition to adding end of line char(s) to the output. Is that only on tty output maybe? I use G++ 3.2.2 iostreams right now, does anyone know if stlport iostreams will fix the problem or has used the stlport version of the iostreams library with quickfix? It doesn't look like specifying -with-stlport in ./configure causes the stlport iostreams library to be linked against any of the test or example apps, so I was wondering if there might be problems with using the stlport version in quickfix or in general? <SoapBox> QuickFix is a great API and has saved me a lot of time and effort when writing apps that require FIX protocol in both Unix and Windows environments. The Text tag strings on Reject messages make it a breeze to figure out what's going on when having to diagnose problems with other vendors that don't always comply with the FIX spec for whatever reason. I recommend the API every chance I get. </SoapBox> Much thanks to Oren and everyone that's contributed to the project. Bud |