Patrick: > What can I tell him?
I think you should say "You're Welcome". He should be aware of the concept of "Bug compatibility", and how it makes no sense for us to perpetuate bad things from clipper if fixing them doesn't create any hardship. In this case, removing one bad line of code doesn't qualify as hardship, and finding it is a good thing. (If on the other hand thousands of lines of code had such issues, we'd want to be more sensitive to reducing the impact on conversion.) -- Brian Hays > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Patrick Mast, xHarbour.com > In the Clipper system: > > CLOSE ALL > SET INDEX TO > > executes without a problem. > > The same code segment with xHarbour dies with an error. > > Should xHarbour not be 100% compatible with Clipper and ignore the > error since no tables are open ? > > I know...that line of code should not have been included in the > program, but the "professionals" who did the original programming left > the code there. > //------------------------------ > > What can I tell him? ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ xHarbour-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xharbour-developers
