Re: [Quickfix-developers] Absence of Symbol in FIX44::NewOrderSingle constructor
Brought to you by:
orenmnero
From: Mike G. <mg...@co...> - 2013-02-18 04:10:32
|
On Feb 17, 2013 4:27 PM, "K. Frank" <kfr...@gm...> wrote: > First, could someone give me a quick explanation about the difference > between a "field" and a "component"? Is this something defined in FIX, > or is it a distinction specific to QuickFIX? FIX protocol distinction. As far as the quickfix data dict is concerned, "component" is like "include". > If it's a FIX concept, is it something new to FIX 4.4 Correct. > > My second question appear in line, below: > > On Fri, Feb 15, 2013 at 5:38 PM, Grant Birchmeier > <gbi...@co...> wrote: > > I think you nailed it. The difference in the data dictionary is > > causing the generator to generate the constructor slightly > > differently. > > It's very interesting to me to hear that you use a code generator, that, > I presume, reads the data dictionary. Correct. > > Am I correct that the source bundle I downloaded, quickfix-1.13.3.zip > (or the nearly identical linux version, quickfix-1.13.3.tar.gz) contains > the output of the code generator, but not the generator itself? Contains both the generated files and the generator. See the spec/ dir. > > I think your workaround is the correct way to go. (To be honest, it's > > probably the only way to go.) > > It seems very reasonable, if a little imperfect to use the two-step > construct / set process. > > > Of course, if you want to try your hand at extending the generator to > > include required component fields in ctors, I'm sure the patch will be > > welcome :) > > I doubt I would have the strength for that, but if I wanted to look into > it, where would I find the generator, and information on how to run the > upstream build process, i.e., the part that builds and runs the generator, > instead of just using its output? Just cd spec/ and run the generate script. Then build as usual. |