This would create an incompatibility, but would at the
same time solve the reentrancy problem the original
implementation had. Even better it would also completely
make the class implementation unnecessary (or maybe even
easy to rework to be a layer rather than a copy).
All this in 1.1.
pdfInit returns aReport only for pdf_demo.prg.
In my code I never use aReport.
A typical prg for me is:
pdfInit()
pdfOpen( cPdfFile )
...
pdfNewPage()
pdfXyz()
...
pdfClose()
<open|send|print> cPdfFile
I see this, but what if there is an MT program
trying to generate multiple pdfs at the same
time, or a non-MT one, which happens to use this
lib in a reentrant way?
This will currently fail badly.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
