Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Foxpro Life
Message
 
To
15/04/2017 16:39:25
Walter Meester
HoogkarspelNetherlands
General information
Forum:
Visual FoxPro
Category:
Contracts, agreements and general business
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Network:
Novell 6.x
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01649781
Message ID:
01650248
Views:
56
>>... Of course, for some time now, I've been using mdot, so all my programs since then are share-safe in that respect. If I were to share any utility programs that you'd find helpful, you could use them with confidence.
>>*
>
>Nope.... Again if there are even loopholes in the vast GDI+ libraries (on VFPx) why should I be confident with yours unless I make sure my fieldname convention would be such it won't conflict with it ?

Unfortunately, your field schema does not guarantee anything. You said it yourself that it would work only in combination with your variable naming convention. So, either one makes sense only in combination with the other, and only within the namespace of your project. Any outside program not using mdot could create conflicts since it is not aware of your field naming conventions...
At this point, I think I squeezed every possible answer, at least twice :) I'm not sure what else I can say... Enjoy your weekend!

Sorin

Update: I just looked over the programs in the System GDI+ project. It's all mdotted; no loopholes there. So, apparently most people doing this kind of stuff are actually writing code responsibly.
*
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform