Wayback Machine
- February 2010 (1)
- December 2009 (2)
- November 2009 (3)
- August 2009 (1)
- July 2009 (3)
- June 2009 (7)
- May 2009 (4)
- April 2009 (1)
- March 2009 (1)
- February 2009 (3)
- January 2009 (2)
- October 2008 (2)
- September 2008 (4)
- May 2008 (1)
- March 2008 (1)
- September 2007 (2)
Tags
administration autodie Benchmark bug reporting coding style continuous integration CPAN::Site darkpan DateTime Devel::NYTProf development documentation Exporter ExtUtils::MakeMaker maintenance modern perl modules Moose MyCPAN::App::DPAN MyCPAN::Indexer open source parrot performance perl 5 perl 6 Perl::Critic Pod::Coverage policy development PPI profiling programs rakudo Readonly roles Strawberry Perl Test::Object testing things I like tools twitter upgrading using Perl::Critic xs yapc yapcna2009
Monthly Archives: February 2009
Dealing with the differences in the ways that the CME and the ICE use FIX has been interesting. Some of the differences are simply, oh, this one does things this way and this other one does things another. And some of them are, this is what I expect should be normal and why the hell is this exchange doing things like this? This ends up being reflected in the code.
I’ve got a base message class with a subclass for each exchange. For the former kind of differences, I’ve got an abstract method on the base class with the appropriate implementations on the subclasses. For the “WTF?” things, I’ve got a default implementation on the base class, and override that on the specific subclass.

