Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
#Define oddity
Message
De
13/12/2004 03:05:07
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Titre:
Versions des environnements
Visual FoxPro:
VFP 6 SP5
OS:
Windows XP SP1
Database:
Visual FoxPro
Divers
Thread ID:
00968604
Message ID:
00968675
Vues:
9
>Hi Gregory,
>
>>Anyone can reproduce / explain the code below ?
>
>I agree with Sergey that this is a bug in VFP. It looks like it's related to "aa" being the first string in the #DEFINE statement. As soon as you insert another character in front like "m.aa=aa", "?aa=aa", "(aa=aa)", etc., the replacement works correctly.
>
>--
>Christof

hi Christof,

I was thinking along these lines too when I got up this morning. It's as if they were starting to scan from the second char.

thanks,
Gregory
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform