most probably the header #- that causes some trouble.
Arjan Scherpenisse wrote:
Martin Kersten wrote:
That's a real pity. Would it require many changes? Otherwise, we would have to invalidate the perl API in the upcoming release.
I dont know if it requires many changes. The reply-parsing code in monet.pm looks quite 'unstable' to me; I have not found the problem yet.
In my opinion it would be better to base programming language APIs on the existing libMapi C code. That way protocol changes etc. only need to be implemented in a single place...
Anyway I do not think I have much time to look further into this, I have a thesis to finish ;-)
Arjan
Arjan Scherpenisse wrote:
Martin Kersten wrote:
Does it run against our current DBI?
No, it does not run. Connecting works, and executing queries too, but fetching results from queries does not.
It is likely that this is the case because it is a pure-perl implementation and it is not up-to-date with some of the changes in the protocol lately.
Even the simple test script which comes with the current implementation does not run anymore :(
Arjan