Re: [patch] export OLE fields

Brian Bruns <[email protected]> Mon, 7 Feb 2011 18:38:35 -0500
Newsgroups gmane.comp.db.mdb-tools.devel
Message-ID <[email protected]>
Hi Nirgal,

You are spot about why we are fprintf()'ing to stdout.  It would have
made it easier to search/replace and do something useful with the
output later.  The OLE stuff was all very nascent and I was still
trying to figure out how to make sense of it, thus the state it was
in.

Quite a few patches from you in the past two days.  I'm going to try
to sort through them tonight if I can (been fighting a nasty cold),
and if not early this week definitely.

Brian

2011/2/7 Nirgal Vourgère <[email protected]>:
> On Monday 07 February 2011 22:12:58 Thomas Adam wrote:
>> Why not just printf() as it will print to STDOUT anyway.  Same comment for
>> the other occurances it happens for in this patch.
>
> I simply kept the ... strange ... existing convention for the code around.
> Maybe one day this may write to a real file. Just maybe...
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> mdbtools-dev mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mdbtools-dev
>

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb