On Sat, 03 Aug 2002 22:34:45 -0400, Greg M. Johnson quoth:
> I have a huge file full of Megapov's> $a = 0;> $b = 0;> etc.> > When I tell 3.5 to replace> $> with> #declare> it insists on making it> #DECLARE.
Did you have "preserve case" checked in the replace dialog? The $
character might be considered a capital letter.
--
Mark
From: hughes b
Subject: Re: editor bug? or something...?
Date: 4 Aug 2002 01:20:45
Message: <3d4cb9ad$1@news.povray.org>
"Greg M. Johnson" <gregj:-)56590@ao:-)l.com> wrote in message
news:3d4c9361@news.povray.org...
> I verified the following problem before reporting.> The I tried agaaaiiiin and it behaves perfectly logically.
Maybe only the Preserve Case and Match Case confusion I always run into when
I am not paying attention to what the setup is. I keep thinking both can be
on and not encounter a surprise. Wrong. I leave Preserve Case off and only
use Match instead so I can be fairly certain things will go right the first
time.
Maybe there is something kind of puzzling about Preserve Case anyhow. I've
seen it add or take away capital letters which seemed incorrect. Like you
said, all letters might become capitalized or as just happened to me today
only the first letter remained capitalized and the rest went to lower case.
Could be that I never get the proper usage of it but I do find using Match
and not using Preserve to be the better choice for the times I've used
Search, Replace. Having gone in and tried some more with it I couldn't seem
to rely on the outcome Preserve gave me.
Let me show an example so everyone knows what I am doing here:
Selected a identifier called WoodBoard then going to Search and Replace I
put woodBoard as the new word. Preserve Case checkboxed, nothing else. What
happens is I get Woodboard, capitals are switched around. Probably because
it tells the editor to preserve the original capitalization and then loses
the "B" due to it being one word. Pretty much what a word editor would try
and do. I can't remember the whole word becoming capital letters though,
such as happened for you.
I think this was told of some time back by someone else.
P.S.
Oh hey now, this was interesting. I tried the $a replaced by #declare just
now and had a Access Violation error. Closed the error and tried a second
time (I had put two $a lines to test with) and it went fine, #declare
written over it.
So perhaps a little strain on the editor to do special replacements like
that? Don't know how special a $ and # might be but makes sense there could
be some internal language oddities anyway. I sure wouldn't know the inner
workings.
