Bill:
Thanks for the call out. But the right answer was given. However, BDT
should have a right clickable menu item for toggling commented code blocks.
Regards,
Doug
www.u2lgoic.com/tools.html
'When BDT is not good enough try XLr8Editor"
On Thu, Jan 10, 2013 at 8:56 AM, Bill Brutzman wrote:
>
My apologies - I did not spot that
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bobby Worley
Sent: 10 January 2013 15:28
To: U2 Users List
Subject: Re: [U2] {BDT] Commenting A Block Of Code
The OP (bill) in
Victory...
Thanks Ross... for the best answer.
Thanks also to Troy, Charles, Brian, Bobby, Dave, Will, Wol, Symeon, Peter, and
John-Boy... for responding.
I am shocked... that I did not see anything from Doug.
--Bill
___
U2-Users mailing list
U2-Use
Don't know if someone mentioned $DEFINE and $IFDEF, but you can do this to
comment out blocks of code.
$DEFINE DEBUG
later enclose the code in a $IFDEF/$ENDIF block.
$IFDEF DEBUG
Code to be commented out
$ENDIF
Then to bring it back undefine DEBUG or move the $IFDEF statement.
Charles
Even better would be to use a $IFDEF so the compiler strips it out, and that
way it's not confused with other Ifs.
Brian
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dave Davis
Sent: 10 January 2013 15:15
To: U2
The OP (bill) included {BDT] in the subject line so he is asking about
Basic Developer Toolkit.
the Ctrl-/ answer is correct.
On Thu, Jan 10, 2013 at 2:49 AM, Symeon Breen wrote:
> The big question is which editor ? Winted, Unidebugger, BDT , etc ?
>
>
>
>
> -Original Message-
> From
You could surround the lines with an IF statement that always evaluates to
false.
Not the same as commenting out of course.
IF (0) THEN
Code you don't want to run.
END
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behal
Not G11 ?
Ok I'm kidding
-Original Message-
From: Wols Lists
To: u2-users
Sent: Thu, Jan 10, 2013 3:18 am
Subject: Re: [U2] {BDT] Commenting A Block Of Code
On 10/01/13 01:55, Peter Cheney wrote:
> Hi Bill,
>
> In UV's ED use the < (start block) and > (end block) to define a
On 10/01/13 01:55, Peter Cheney wrote:
> Hi Bill,
>
> In UV's ED use the < (start block) and > (end block) to define a block of
> code.
> Then do C//*/B
> This will prompt for confirmation of change block from line n through m.
>
Hmmm that's new to me ...
What I would have done - let's say
Bill
Different options in ascending order of usefulness:
1. In ED, use block commands to start and finish and then replace the start
of each line, e.g.
10 (goes to line 10)
< (starts block)
20 (goes to line 20)
> (ends block)
c//*/B (comments block)
2. In Z (free from my site), use the cursor
The big question is which editor ? Winted, Unidebugger, BDT , etc ?
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Brutzman
Sent: 10 January 2013 01:25
To: U2 Users List
Subject: [U2] {BDT] Commenting A Block
11 matches
Mail list logo