bit and nibble variable types, debugger suggestion

[alsopb]

It would be nice to add bit and nibble variable types to save a few bits.
Packing flags into variable bytes of course can be done, as can packing nibbles into a byte. It would be a bit cleaner to just have bit and nibble variable types.

Have quite a few uses for nibbles since ham radio gear represents some outputs in 4 bit BCD code.

On the debugger, it would be nice to actually be able to step through procedures as well as the main program lines. Bad programming in procedures would be a lot easier to detect. If this feature already exists, I'd like to know how to turn it on.

Regards
Brian
Henderson, NC

[zristic]

It would be nice to add bit and nibble variable types to save a few bits.

Let's see what the optimizations will bring to us.

On the debugger, it would be nice to actually be able to step through procedures as well as the main program lines. ... If this feature already exists, I'd like to know how to turn it on.

Once positioned to a procedure call, just press F7. The debugger will enter the procedure (if this was the question?).

[alsopb]

Thank you. F7 does the trick.
Couldn't find it in documentation.

My ignorance of IDE terminology is getting in the way.

I guess one could interprete "step into" on the pull down menu as meaning enter procedure when positioned at call line.

Now if I could figure out what "step out" (ctrl-F8) means. It seems to run the program with the watch box open. However the values in the watch box doen't seem to change.

Is there a reference detailing what each of the IDE interface options?

Regards
Brian

[zristic]

what "step out" (ctrl-F8) means.

It runs until it exists the current procedure.

Is there a reference detailing what each of the IDE interface options?

Working on it.

[hansolo]

Zoran,

How about the request for bit and nibble variable types?

Will it be implemented?

Just a reminder.

HC Wong

[zristic]

How about the request for bit and nibble variable types?

On the waiting list.