Closed GoogleCodeExporter closed 8 years ago
Michael,
Any chance you could take a look at what's causing this? It may be in Mutilslibs
I'm a bit swamped this week.
Mark
Original comment by mark.th...@gmail.com
on 5 Jun 2011 at 11:48
Hi Mark,
See attached a patch to MUTILSLIB that fixes this problem, d-style.
The problem is that an error in opening a log file, well, cannot really be
written to a log file ..
Hence my solution is to return 'err' and 'message', like in all DMSL prox. The
calling proc should then check if err==EXIT_SUCCESS, and take action
accordingly.
I made them optional, which means that your existing code will still compile
(but will not have access to the improved functionality).
NB: This patch is needed for BATEA / DMSL r419+.
cheers,
d
Original comment by dmitri.k...@gmail.com
on 23 Jun 2011 at 2:39
Attachments:
Implemented in r101 of MUtilslib. The branch\ver-3.0.x now links to this
revision of MUtilslib and hence this issue is resolved.
Original comment by mark.th...@gmail.com
on 2 Jul 2011 at 5:44
Original issue reported on code.google.com by
dmitri.k...@gmail.com
on 1 Jun 2011 at 5:27