|
Out of curiosity, a full heavily threaded MS stack running over a unix odbc layer or I misunderstand? Are you guys masochistic? :D :P
Seriously, print based "debugger" won't get spectacularly far, at minimum a coredump and gdb or similar.
I agree with you that this async everywhere - is - kool is pretty debatable, especially when calling in external code, that can serialize anyway certain critical section anyway... and especially when talking then to remotes that have different constraints... async has is place, it is nice to have it as option, but as the default mode of functioning and modeling of code ... ehm.. .no... should be a deliberate choice (in some modules)... IMHO obviously
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.