> I've been working on updating a parser that I've written in C++ for a > couple of weeks now.
> This stems from my need to > deploy it within our firm and not deploy Perl/Python/Java/etc. I think it's great to have more choice for the steps of the chain, for exactly the reason that you mention, that components can be swapped in and out to make a solution that is the best match for the goal. (1) An interface. Choice of: -some command line interface for better automation, or users who prefer CLI -some graphical user interface for users familiar with GUIs (2) A parser. Best fit for the job with choice of: -Python -Perl -C++ -Java (3) With perhaps a choice of image parsers. (4) Output can be used by different readers. Choice of -Palm viewer -Viewer on desktop -Viewer on other PDA devices (zaurus, etc) The key that keeps things running so nicely is documented APIs, and using the Plucker standards to allow I/O between any of the tools along the Plucker chain. The more solutions that are available for someone wanting to deploy, a better fitting solution can be deployed. Best wishes, Robert _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
