Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Bindevent to a property
Message
De
10/04/2013 15:54:29
 
 
À
10/04/2013 15:37:41
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Divers
Thread ID:
01570434
Message ID:
01570665
Vues:
65
>>The sad thing about Thor is that it also has the ability to validate whether or not there are any name collisions on a system when you know all of the tables in use, and have all the source code, yet such a report will not be created due to reasons specific to its developers' beliefs that the only proper solution is to prefix everything with "m." on variables.
>
>Rick --
>
>Please explain this statement. As far as I know, and I am the creator of Thor, there is
>no belief "that the only proper solution is to prefix everything with "m." on variables."
>In fact, I do not use use M.Dots (horrors!), nor have I ever encountered name conflicts
>as result thereof

There's a thread about it in the Google Groups group for Thor. In that thread, I asked that this functionality be added a couple months back. After several back and forth exchanges, I was told (in short) that wasn't going to happen. I've since left the group and moved on.

>I am not aware of any "ability to validate whether or not there are any name collisions on
>a system when you know all of the tables in use". There are, indeed, some small bits and
>pieces in Thor that could be used to address such a request, but there is nothing like what
>you are asking for. It would be a significant amount of new work to achieve it.

It would not be significant. Only a project or directory would be required. You iterate through every file, parsing every table, every program, class, form, etc., and identify every variable reference, and every field name. Note any collisions.

The code which prefixes everything with "m." in Thor right now could be extended to also record this data to a table. And a simple SQL SELECT statement at the end would list any collisions.

>Beyond that, if you want to contribute code to address this issue that you identify as so
>sadly missing, we would all welcome your contribution. The tools in Thor have been
>accumulated from many contributors. We would love it if you could be the newest
>contributor.

This functionality will (James 4:15) be present in Visual FreePro.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform