Other F7 Rename in conditional compilation blocks.

LucaMs

Expert
Licensed User
Longtime User
I was about to write a bug report; "luckily" I did other tests first

F7 Rename had not worked well for me; some constants had not been renamed. I found this to happen in lines in conditional compilation blocks. Then, however, I tried and the renaming also happens in those blocks, when they are "active", that is, I set the configuration with the "right" compilation symbol.

I wonder if it is good for this to happen or not
 
Sort by date Sort by votes

LucaMs

Expert
Licensed User
Longtime User
Erel said:
Renaming cannot work in excluded code. The renaming feature relies on the compiler outputs and the excluded code is ignored by the compiler (it must be).
Click to expand...
Yes, I understand this, technically; but what happened to me will probably happen often, I was calm that I had renamed some constants everywhere in the project.

Anyway, even if with some difficulty, I was able to correct my "bug", since the compilation clearly highlighted the problem.
 
Upvote 0
You must log in or register to reply here.

Similar Threads

  • Locked
  • Article
B4J Library XLUtils / jPOI 5 - Read and write MS Excel workbooks
2
Replies
20
Views
18K
Erel
Bug? Renaming a routine to make it a property
Replies
5
Views
769
LucaMs
Bug? Version 8.50 - F7 "Rename to" is missing
Replies
9
Views
1K
LucaMs
Bug? [Not A Bug - By Design] Rename To > "Name Already Exists"
Replies
1
Views
1K
Erel
Bug? B4J Rename To: - possible bug?
Replies
6
Views
1K
Erel
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…