J
Jeff Ledbetter
Guest
Thanks. I didn’t know that it had been discussed previously. A customer reported it us when trying to compile their code with their Roundtable database connected. :-\ Jeff Ledbetter www.roundtable-software.com email: jeff.ledbetter@roundtable-software.com skype: jeff.ledbetter From: Mike Fechner [mailto:bounce-mikefechner@community.progress.com] Sent: Sunday, March 15, 2015 12:08 PM To: TU.OE.Development@community.progress.com Subject: [Technical Users - OE Development] AW: Bug With Unqualified Class Reference? AW: Bug With Unqualified Class Reference? Reply by Mike Fechner Since a very long time the compiler prefers abbreviated table names where you want to refer to a class name with the help of using. It was discussed a couple of times in this form as well. It's is truly annoying and a time bomb. Code that compiles in our framework may fail to compile when used at one of our clients with their databases connected. Von meinem Windows Phone gesendet Von: Jeff Ledbetter Gesendet: 15.03.2015 17:57 An: TU.OE.Development@community.progress.com Betreff: [Technical Users - OE Development] Bug With Unqualified Class Reference? Bug With Unqualified Class Reference? Thread created by Jeff Ledbetter Hi. This fails: USING System.IO.*. message Path:GetRandomFileName() view-as alert-box. with the error " ** Path is ambiguous with rtb_path.path-guid and rtb_pname.path-guid (72)" The following works: message System.IO.Path:GetRandomFileName() view-as alert-box. This behavior was observed on OE 11.3.2. This seems like a bug to me. Stop receiving emails on this subject. Flag this post as spam/abuse. Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...