JK>Dear Dave and PowerBASIC tech staff:
JK>        Please let me know how I should proceed.  If it comes down to
JK>        it, I'm going to have to rewrite 5,000 lines of code at the cost
JK>        of another $25,000 of my time.  And all for a $19.95 upgrade.
JK>        
Jamshid,
What do you think we should do?  Internally, we have switched all
projects (large and small) over to PowerBASIC 3.2 without any problems.
Additionally, PowerBASIC 3.2 has been shipped to tens of thousands of
customers at this point.  And I have received no such reports from any
of those customers.
Not to say that you haven't found a legitimate problem or bug.  But
based on your message, how should we go about finding it?  Nothing we
have produces it.  How do you find a bug which you can't reproduce?
You have to look at this from our point of view.  We receive hundreds of
bug reports a *week* and only 1 out of about 5,000 turns out to be a
legitimate bug.  99.9% of the time it's user error.
I agree that if something compiles fine under 3.1, it should compile
fine under 3.2.  However, you mention in your message that you have
ported over a lot of it to features of PowerBASIC 3.2.  Therefore, I
would have to suspect that the problem lies in the code which has been
modified.  Likely to be user error on your part during the 'porting'
process.  If you have code which you can send us which actually
demonstrates the problem, we'd be happy to take a look at it and fix it,
if indeed it is a problem with the compiler.  But without something to
demonstrate the problem on our end, there's little help that I can
offer.  I hope you understand.
--Dave
---
 * QMPro 1.53 * CCITT- Can't Conceive Intelligent Thoughts Today
--- WILDMAIL!/WC v4.12 
---------------