| Re: .skip [message #23578] |
Tue, 30 January 2001 08:43 |
Pavel A. Romashkin
Messages: 531
Registered: November 2000
|
Senior Member |
|
|
Jaco van Gorkom wrote:
>
> PS: The other reason: .SKIP is not in David's book. Of course it is
> not,
> him not needing it, writing only perfect code. Now as for his readers...
... that are supposed to be approaching the same level of perfection as
they go through the book ... :-)
Cheers,
Pavel
|
|
|
|
| Re: .skip [message #23587 is a reply to message #23578] |
Tue, 30 January 2001 02:32  |
Jaco van Gorkom
Messages: 97
Registered: November 2000
|
Member |
|
|
Reimar's list of IDLDE menu items pinpoints exactly one of the two
reasons why I never used .SKIP until a few months ago: I never found
it, it's nowhere in the IDLDE menus! So maybe you could add the
request for a menu item to your bug report?
cheers,
Jaco
PS: The other reason: .SKIP is not in David's book. Of course it is
not,
him not needing it, writing only perfect code. Now as for his readers...
----------------
Jaco van Gorkom e-mail: gorkom@rijnh.nl
FOM-Instituut voor Plasmafysica "Rijnhuizen", The Netherlands
>> You have never used .SKIP?! Well, it's very useful when you write a
>> line with a bug that causes your program to crash. People who write
>> IDL code without any bugs, of course, would have no need of this command.
>>
>> cheers,
>> Mark
>
> Dear Mark,
>
> if you have a real good development tool you will have some more or
> different tools as only stop and .skip.
>
> In idlde for example I and I am sure David too we are using
> some icon-functions:
>
> Step into
> Step over
> Step out
> Break
> Stop
> Toggle out
> Edit Breakpoints
>
> or some Run commands:
> Trace
> Run to cursor
> Run to return
>
> Profile helps a lot too.
>
> The usage of breakpoints instead of stop is much better.
>
> cheers
>
> Reimar
>
> --
> Reimar Bauer
>
> Institut fuer Stratosphaerische Chemie (ICG-1)
> Forschungszentrum Juelich
> email: R.Bauer@fz-juelich.de
>
> =============================================
> a IDL library at ForschungsZentrum J�lich
> http://www.fz-juelich.de/icg/icg1/idl_icglib/idl_lib_intro.h tml
>
> http://www.fz-juelich.de/zb/text/publikation/juel3786.html
|
|
|
|
| Re: .skip [message #23607 is a reply to message #23587] |
Mon, 29 January 2001 08:34 |
Pavel A. Romashkin
Messages: 531
Registered: November 2000
|
Senior Member |
|
|
I have not been using it for the simple reason: I never found it. Now I
will, and I would like the bug fixed, too.
Thanks,
Pavel
Mark Fardal wrote:
>
> Hi,
>
> The .SKIP command doesn't behave quite the way I would prefer.
> It doesn't behave as advertised either, although for a different reason.
>
> What it is supposed to do is to skip one statement, or N statements if
> you give it an argument N, and then execute 1 statement. I would
> prefer that it not execute that one statement. It seems silly--after
> all, you are usually just going to type .continue--and who's to say
> that you won't decide to skip the next statement too. Besides, it's
> not called .skip-and-execute-one. The usual argument about preserving
> backwards code compatability don't apply here, since .SKIP can't be
> invoked from a program.
>
> But anyway, what it actually does when you type IDL> .SKIP [N]
> is to skip N statements, and then execute N statements. Oops.
> This is with IDL 5.2.1L on Debian linux.
>
> Before I submit a bug report, I thought I would ask whether people
> would like the feature change suggested above as well as the bug fix.
> Or are people emotionally attached to the current behavior?
>
> thanks,
> Mark
>
> PS: here's a simple example to demonstrate the behavior:
>
> pro junk
> print, 'line 2'
> print, 'line 3'
> print, 'line 4'
> print, 'line 5'
> print, 'line 6'
> print, 'line 7'
> print, 'line 8'
> print, 'line 9'
> print, 'line 10'
> end
|
|
|
|
| Re: .skip [message #23615 is a reply to message #23607] |
Mon, 29 January 2001 00:38 |
R.Bauer
Messages: 1424
Registered: November 1998
|
Senior Member |
|
|
Mark Fardal wrote:
>
>> Mark Fardal (fardal@weka.astro.umass.edu) writes:
>>> Before I submit a bug report, I thought I would ask whether people
>>> would like the feature change suggested above as well as the bug fix.
>>> Or are people emotionally attached to the current behavior?
>>
> David writes:
>> It looks like it behaves this way in IDL 5.4 on Windows, too.
>> The good news is I'm not emotionally attached to this behavior,
>> since I have never used it. :-)
>>
>> Submit away!
>>
>> Cheers,
>>
>> David
>
> You have never used .SKIP?! Well, it's very useful when you write a
> line with a bug that causes your program to crash. People who write
> IDL code without any bugs, of course, would have no need of this command.
>
> cheers,
> Mark
Dear Mark,
if you have a real good development tool you will have some more or
different tools as only stop and .skip.
In idlde for example I and I am sure David too we are using
some icon-functions:
Step into
Step over
Step out
Break
Stop
Toggle out
Edit Breakpoints
or some Run commands:
Trace
Run to cursor
Run to return
Profile helps a lot too.
The usage of breakpoints instead of stop is much better.
cheers
Reimar
--
Reimar Bauer
Institut fuer Stratosphaerische Chemie (ICG-1)
Forschungszentrum Juelich
email: R.Bauer@fz-juelich.de
=============================================
a IDL library at ForschungsZentrum J�lich
http://www.fz-juelich.de/icg/icg1/idl_icglib/idl_lib_intro.h tml
http://www.fz-juelich.de/zb/text/publikation/juel3786.html
|
|
|
|
| Re: .skip [message #23619 is a reply to message #23615] |
Sun, 28 January 2001 15:18 |
Mark Fardal
Messages: 51
Registered: October 1995
|
Member |
|
|
> Mark Fardal (fardal@weka.astro.umass.edu) writes:
>> Before I submit a bug report, I thought I would ask whether people
>> would like the feature change suggested above as well as the bug fix.
>> Or are people emotionally attached to the current behavior?
>
David writes:
> It looks like it behaves this way in IDL 5.4 on Windows, too.
> The good news is I'm not emotionally attached to this behavior,
> since I have never used it. :-)
>
> Submit away!
>
> Cheers,
>
> David
You have never used .SKIP?! Well, it's very useful when you write a
line with a bug that causes your program to crash. People who write
IDL code without any bugs, of course, would have no need of this command.
cheers,
Mark
|
|
|
|
| Re: .skip [message #23621 is a reply to message #23619] |
Sun, 28 January 2001 12:04 |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
Mark Fardal (fardal@weka.astro.umass.edu) writes:
> The .SKIP command doesn't behave quite the way I would prefer.
> It doesn't behave as advertised either, although for a different reason.
>
> What it is supposed to do is to skip one statement, or N statements if
> you give it an argument N, and then execute 1 statement. I would
> prefer that it not execute that one statement. It seems silly--after
> all, you are usually just going to type .continue--and who's to say
> that you won't decide to skip the next statement too. Besides, it's
> not called .skip-and-execute-one. The usual argument about preserving
> backwards code compatability don't apply here, since .SKIP can't be
> invoked from a program.
>
> But anyway, what it actually does when you type IDL> .SKIP [N]
> is to skip N statements, and then execute N statements. Oops.
> This is with IDL 5.2.1L on Debian linux.
>
> Before I submit a bug report, I thought I would ask whether people
> would like the feature change suggested above as well as the bug fix.
> Or are people emotionally attached to the current behavior?
It looks like it behaves this way in IDL 5.4 on Windows, too.
The good news is I'm not emotionally attached to this behavior,
since I have never used it. :-)
Submit away!
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: davidf@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
