X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 12 Feb 2008 11:08 AM by  anon
Code folding in IDL7 Workbench
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
12 Feb 2008 11:08 AM
    I have some source files where code folding works just fine and some where it doesn't. Is there any way to "re-index" a particular file containing multiple procedures/functions?

    Deleted User



    New Member


    Posts:
    New Member


    --
    12 Feb 2008 11:08 AM
    Jake: If there is the possibility that this is a bug, then send to ITT Visual Information Solutions Tech Support ('techsupport@ittvis.com') a copy of one of the '.pro' files with multiple routines, which is not able to perform code folding properly. I would not think that code folding should be governed by a very difficult parsing algorithm. I would think that the Java/Eclipse-based workbench would look at all the lines of the '.pro' file, it would find each line that starts with the distinct word "pro" or "PRO", and it would find each ensuing line that starts with the distinct word "end" or "END". If there are problems with how this logic is executing, then I would expect one of the following to be the probable source: 1) Maybe there is a blank space character before the "PRO" or "END" statement? I do not know that this is so, but it is possible that that might violate the Eclipse code-folding rules. 2) Perhaps there is an issue with how newlines/carriage-returns are formatted in the files that you have that are having problems with code folding? Thus, if your IDL Workbench is on Windows, but you are displaying a '.pro' file acquired from a Linux machine, perhaps that poses a problem of code folding? In this case, you might try re-indexing by pasting your code in MS Windows 'Notepad', seeing that it displays properly, then resaving it on Windows. (If your problem were with Windows code displaying in a Linux IDL Workbench, you might try running the Linux utility 'dos2unix' on the Windows-based source code.) 3) Perhaps there is just an error in the matchup of PRO statements to END statements. (A ".COMPILE" call should reveal such a problem, however.) James Jones ITT Technical Support
    You are not authorized to post a reply.