Author Topic: special handling of the macro replacement ""?  (Read 127 times)

Online ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6143
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
special handling of the macro replacement ""?
« on: Today at 06:43:08 am »
Hi, when I'm using the gd_on's unified workspace/code::blocks cbp files, I see something strange.

See here: it looks like GCC works OK, but GDB failed to find the dll(setting wrong PATH)

Re: crash when I try to open a wxsmith file under C::B against wx 3.3.1

If a variable a has a filed name b, and its value is
Code
""
, and if we have
Code
AAA$(#a.b)
, we will finally get
Code
AAA""

The current implementation treats an empty string "" as a valid value and performs the replacement, resulting in
Code
AAA""
instead of the expected
Code
AAA
.

I'd like to see your options on this issue.

Thanks.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 681
Re: special handling of the macro replacement ""?
« Reply #1 on: Today at 09:21:14 am »
Make sure you get approval by MortenMacFlybefore making any changes. Check out the SF tickets for posts on macro and hopefully you will fins the ticket and have a read before you spend time on this as you may end up wasting your time.
BTW I agree with you.

Online ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6143
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: special handling of the macro replacement ""?
« Reply #2 on: Today at 09:33:30 am »
Make sure you get approval by MortenMacFlybefore making any changes. Check out the SF tickets for posts on macro and hopefully you will fins the ticket and have a read before you spend time on this as you may end up wasting your time.
BTW I agree with you.

Hi, AndrewCot,  long time no see.
I think it is a good direction.
Maybe there are similar topics in the sourceforge tickets.
So I will search for that.

To switch between the debug version of wx library,  using the unified workspace or cbp project is much easier.  We don't need to replace or editor each cbp files.


If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.