Topic: Parenthesis matching ... DUH!!!

[Kerry]

Code: [Select]

  ...........
(ACTION_TILE "nyloc" "(_calextra)")
(ACTION_TILE "mk_pick" "(progn(_getparams)(DONE_DIALOG 9))")
(ACTION_TILE "replaceblock" "(progn (SETQ bolt:replace T) (check_eval)")
(ACTION_TILE "eval_length" "(_evallen)")
(ACTION_TILE "accept" "(check_eval)")
(ACTION_TILE "cancel" "(DONE_DIALOG 0)")
.......
No prizes ...  but this had me chasing my tail for a while ...   

[Mark]

Code: [Select]

(ACTION_TILE "replaceblock" "(progn (SETQ bolt:replace T) (check_eval)")
my guess ....

[Kerry]

yep, and damn difficult to find.  ... locks up the routine, and ACAD, dead .. with no error message ..   

[ElpanovEvgeniy]

yep, and damn difficult to find.  ... locks up the routine, and ACAD, dead .. with no error message ..   

Code: [Select]

(ACTION_TILE "nyloc" (VL-PRIN1-TO-STRING '(_calextra)))
(ACTION_TILE "mk_pick" (VL-PRIN1-TO-STRING '(progn(_getparams)(DONE_DIALOG 9))))
(ACTION_TILE "replaceblock" (VL-PRIN1-TO-STRING '(progn (SETQ bolt:replace T) (check_eval))))
(ACTION_TILE "eval_length" (VL-PRIN1-TO-STRING '(_evallen)))
(ACTION_TILE "accept" (VL-PRIN1-TO-STRING '(check_eval)))
(ACTION_TILE "cancel" (VL-PRIN1-TO-STRING '(DONE_DIALOG 0)))


[Mark]

I cheated!

[delium55]

Bonjour Mark,

Just a simple question; how do you check the extra paranthesis with VIM.

[MP]

If the question comes up it's <Ctrl> <M> in Textpad.

[Mark]

Bonjour Mark,

Just a simple question; how do you check the extra paranthesis with VIM.

In that particular instance I simply placed the cursor on each beginning paren, Vim 7 highlights the opening, closing parens by default.

[Joe Burke]

If the question comes up it's <Ctrl> <M> in Textpad.

Michael,

I wish TextPad was smart enough to ignore commented out lines while checking parens with Ctrl M.

[CAB]

Also in UltraEdit placing the cursor causes the matching paren to highlight.

[MP]

Michael,

I wish TextPad was smart enough to ignore commented out lines while checking parens with Ctrl M.

That's a good idea (as an toggled option) Joe, I'll pass that on to the Helios folks when I get a chance. Thanks.

[qjchen]

when use Pspad, type the left Parenthesis, the right Parenthesis automatic generate, when point to the left Parenthesis, it automatic found the Parenthesis.

Lisplink use ctrl+M to find the matching. and its ctrl+A is very useful for me.

Fig.1 Pspad, Fig.2 Lisplink

[Kerry]

Thanks guys,

It wasn't so much the capability of checking matching paren's  line by line ..

.. more the fact that we have to know where to look.

Because AutoCAD freezes when it tries to evaluate the callback, any debugging and animation/tracing is suspended as well .. so I thought the problem was in the (check_eval) function ; but only under certain conditions 'cause it is called from other locations as well.
Resolved the location by using debug:print statements. .. just tedious !

Sort of an anticlimax to discover the cause, I tell you.

[MickD]

It's allways something simple
I know just how you feel, I had a lot of these moments lately!

[Andrea]

now if you talk about lisp editor...
 
I use this....

http://www.studioware.com/

[Kerry]

PERSONAL OPINION :

Anyone learning lisp, Vlisp may be better served using the VLIDE from Autocad, to take advantage of ;
Integrated Help,
Integrated formatting,
Integrated debugging  < this is a biggie >
Integrated Intellisense < for want of a better expression >

Appropos,
In line evaluation.
etc, etc, etc.

I believe that a lot of questions I see on forums could be resolved by use of the VLIDE.


Note : I have read arguments that using any integrated editor is evil .. and I don't want to get involved in that discussion here.

[ElpanovEvgeniy]

Completely with you i agree!
I too use VLIDE from Autocad...

[CAB]

I too use VLIDE as my primary editor & it's great for debugging & formatting. I use a secondary editor for it's "Column Mode" and other features ("projects" is a nice one). Also to hold files I use for "Cut & Paste" of code sections. This reduces the open files in VLIDE.

[Jeff_M]

I believe that a lot of questions I see on forums could be resolved by use of the VLIDE.

AMEN brother Kerry! It is so easy to check/run just one line, or even one chunk, of code that may, or may not, be the source of your problem.

Personally, I don't care what editor that they use to code in. I just wish that if/when they have problems they'd at least place it into the VLIDE and check it for problems and/or set a break point and step through it themselves.