comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » function/procedure/keyword list for use in creating an editor syntax description
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
function/procedure/keyword list for use in creating an editor syntax description [message #84798] Tue, 11 June 2013 13:27 Go to next message
Paul Van Delst[1] is currently offline  Paul Van Delst[1]
Messages: 1157
Registered: April 2002
Senior Member
Hello,

I guess this mostly a question for the Exelis folks who read this ng...

I just started using the kate editor and while I was pleasantly
surprised there was an existing RSI-IDL syntax definition file it was
for v5.x of IDL. I want to upgrade the syntax defn file.

So, my question: Is there an easy way to obtain a current list of the
v8.2.x IDL functions/procedures/keywords? E.g. some magic, undocumented
IDL command? Or on the Exelis website perhaps?

If there is not, is this something that Exelis would consider publishing
in the future?

ccheers,

paulv
Re: function/procedure/keyword list for use in creating an editor syntax description [message #84807 is a reply to message #84798] Tue, 11 June 2013 18:22 Go to previous messageGo to next message
Michael Galloy is currently offline  Michael Galloy
Messages: 1114
Registered: April 2006
Senior Member
Paul van Delst <paul.vandelst@noaa.gov> wrote:
> Hello,
>
> I guess this mostly a question for the Exelis folks who read this ng...
>
> I just started using the kate editor and while I was pleasantly surprised
> there was an existing RSI-IDL syntax definition file it was for v5.x of
> IDL. I want to upgrade the syntax defn file.
>
> So, my question: Is there an easy way to obtain a current list of the
> v8.2.x IDL functions/procedures/keywords? E.g. some magic, undocumented
> IDL command? Or on the Exelis website perhaps?
>
> If there is not, is this something that Exelis would consider publishing in the future?
>
> ccheers,
>
> paulv

I have some scripts that parse the online help to give a list of routine
names.

Mike
--
www.michaelgalloy.com
Research Mathematician
Tech-X Corporation
Re: function/procedure/keyword list for use in creating an editor syntax description [message #84809 is a reply to message #84798] Tue, 11 June 2013 18:59 Go to previous messageGo to next message
wlandsman is currently offline  wlandsman
Messages: 743
Registered: June 2000
Senior Member
;list of procedure names
IDL> print,routine_info(/system)

;list of function names
IDL> print,routine_info(/system,/func)

These won't list the procedures/functions stored as dlm's, e.g.

IDL> help,/dlm

I'm not sure how to get the names of the procedure/functions stored in the DLMs.

--Wayne

On Tuesday, June 11, 2013 4:27:27 PM UTC-4, Paul van Delst wrote:
> Hello,
>
>
>
> I guess this mostly a question for the Exelis folks who read this ng...
>
>
>
> I just started using the kate editor and while I was pleasantly
>
> surprised there was an existing RSI-IDL syntax definition file it was
>
> for v5.x of IDL. I want to upgrade the syntax defn file.
>
>
>
> So, my question: Is there an easy way to obtain a current list of the
>
> v8.2.x IDL functions/procedures/keywords? E.g. some magic, undocumented
>
> IDL command? Or on the Exelis website perhaps?
>
>
>
> If there is not, is this something that Exelis would consider publishing
>
> in the future?
>
>
>
> ccheers,
>
>
>
> paulv
Re: function/procedure/keyword list for use in creating an editor syntax description [message #84816 is a reply to message #84798] Wed, 12 June 2013 02:34 Go to previous messageGo to next message
Fabzi is currently offline  Fabzi
Messages: 305
Registered: July 2010
Senior Member
On 06/11/2013 10:27 PM, Paul van Delst wrote:
> I just started using the kate editor

I am sorry to ask this, but what are the reasons for not using eclipse
or what are the reasons to use something else than eclipse?

I think I can understand that the emacs/vi fans out here can't get along
without their shortcuts. But what is so great in the Kate editor for
example that could justify spending the time to define a new syntax
description file?

I'm not opening any troll here: I really want to know if I am missing
something important (because I like Eclipse, I learned programming with
Eclipse)

Thanks!

Fab
Re: function/procedure/keyword list for use in creating an editor syntax description [message #84817 is a reply to message #84798] Wed, 12 June 2013 02:47 Go to previous messageGo to next message
Lajos Foldy is currently offline  Lajos Foldy
Messages: 176
Registered: December 2011
Senior Member
On Tuesday, June 11, 2013 10:27:27 PM UTC+2, Paul van Delst wrote:
> Hello,
>
>
>
> I guess this mostly a question for the Exelis folks who read this ng...
>
>
>
> I just started using the kate editor and while I was pleasantly
>
> surprised there was an existing RSI-IDL syntax definition file it was
>
> for v5.x of IDL. I want to upgrade the syntax defn file.
>
>
>
> So, my question: Is there an easy way to obtain a current list of the
>
> v8.2.x IDL functions/procedures/keywords? E.g. some magic, undocumented
>
> IDL command? Or on the Exelis website perhaps?
>
>
>
> If there is not, is this something that Exelis would consider publishing
>
> in the future?
>
>
>
> ccheers,
>
>
>
> paulv


If XML data mining is acceptable:

/usr/local/exelis/idl82/help/idl_catalog.xml

regards,
Lajos
Re: function/procedure/keyword list for use in creating an editor syntax description [message #84824 is a reply to message #84816] Wed, 12 June 2013 06:37 Go to previous messageGo to next message
Andy Sayer is currently offline  Andy Sayer
Messages: 127
Registered: February 2009
Senior Member
Fabien:

The text editor I use to code on Windows(ConText) has, similarly, a fairly outdated IDL highlighter. Turning your question around, what is it about Eclipse that means I would want to use it instead? I went on the Eclipse website but was a bit overwhelmed by the large number of links/projects there (did not know where to start looking). I had not heard of Eclipse until you mentioned it.

(Basically all I want is a text editor with a syntax highlighter and ideally the ability to save to a network drive. On my Mac I use TextWrangler, but there is no Windows version of that.)

Thanks,

Andy

On Wednesday, June 12, 2013 5:34:42 AM UTC-4, Fabien wrote:
> On 06/11/2013 10:27 PM, Paul van Delst wrote:
>
>> I just started using the kate editor
>
>
>
> I am sorry to ask this, but what are the reasons for not using eclipse
>
> or what are the reasons to use something else than eclipse?
>
>
>
> I think I can understand that the emacs/vi fans out here can't get along
>
> without their shortcuts. But what is so great in the Kate editor for
>
> example that could justify spending the time to define a new syntax
>
> description file?
>
>
>
> I'm not opening any troll here: I really want to know if I am missing
>
> something important (because I like Eclipse, I learned programming with
>
> Eclipse)
>
>
>
> Thanks!
>
>
>
> Fab
Re: function/procedure/keyword list for use in creating an editor syntax description [message #84826 is a reply to message #84824] Wed, 12 June 2013 06:53 Go to previous messageGo to next message
Fabzi is currently offline  Fabzi
Messages: 305
Registered: July 2010
Senior Member
Hi Andy,

On 06/12/2013 03:37 PM, AMS wrote:
> what is it about Eclipse that means I would want to use it instead?

Sure, it's a valid question.

The first argument that comes to mind is that IDL (since V7) is using
eclipse as out-of-the-box workbench. That means that (at least) a few
people are thinking about how to integrate best the IDL features into
the workbench (I hope so;-)).

Second, Eclipse is Open Source and has been developed and used for many
many other languages, so it is well known and still an active project.
It is organized in "views" and "projects" and supports SVN (usually very
easily but with IDL it is sometimes a pain :()

Third, (this is where your own habits or tastes comes into the game), it
has cool features and shortcuts. I like how fast I can navigate in the
code using CTRL+F3 for example, I like auto-completion (CTRL+Space), I
like the auto-indenting (CTRL+SHIFT+F), and many other small things.
What Eclipse doesn't have is Emacs-Style programming (not to my
knowledge, but possibly someone made something similar happen in eclipse
too)

The third point is where other people might find it faster to use
another editor... But I always wonder why, so I am asking ;-)

Cheers,

Fab
Re: function/procedure/keyword list for use in creating an editor syntax description [message #84827 is a reply to message #84826] Wed, 12 June 2013 07:02 Go to previous messageGo to next message
Andy Sayer is currently offline  Andy Sayer
Messages: 127
Registered: February 2009
Senior Member
Hi Fabien,

Thanks for the info; auto-indent and so on are nice features. So maybe I should swap to that on the Windows machine.

But which download from these fourteen is the basic text editor I'd want to use? http://www.eclipse.org/downloads/ And is the IDL highlighter included?

I thought maybe this one, although the page doesn't explain too much what is there: http://www.eclipse.org/downloads/packages/eclipse-classic-42 2/junosr2

(Note I don't use Workbench or anything, I compile/run from command line, and also only code in IDL/Fortan/C so don't need bells and whistles or things for other languages.)

Thanks (and sorry for the threadjacking),

Andy

On Wednesday, June 12, 2013 9:53:13 AM UTC-4, Fabien wrote:
> Hi Andy,
>
>
>
> On 06/12/2013 03:37 PM, AMS wrote:
>
>> what is it about Eclipse that means I would want to use it instead?
>
>
>
> Sure, it's a valid question.
>
>
>
> The first argument that comes to mind is that IDL (since V7) is using
>
> eclipse as out-of-the-box workbench. That means that (at least) a few
>
> people are thinking about how to integrate best the IDL features into
>
> the workbench (I hope so;-)).
>
>
>
> Second, Eclipse is Open Source and has been developed and used for many
>
> many other languages, so it is well known and still an active project.
>
> It is organized in "views" and "projects" and supports SVN (usually very
>
> easily but with IDL it is sometimes a pain :()
>
>
>
> Third, (this is where your own habits or tastes comes into the game), it
>
> has cool features and shortcuts. I like how fast I can navigate in the
>
> code using CTRL+F3 for example, I like auto-completion (CTRL+Space), I
>
> like the auto-indenting (CTRL+SHIFT+F), and many other small things.
>
> What Eclipse doesn't have is Emacs-Style programming (not to my
>
> knowledge, but possibly someone made something similar happen in eclipse
>
> too)
>
>
>
> The third point is where other people might find it faster to use
>
> another editor... But I always wonder why, so I am asking ;-)
>
>
>
> Cheers,
>
>
>
> Fab
Re: function/procedure/keyword list for use in creating an editor syntax description [message #84839 is a reply to message #84827] Wed, 12 June 2013 15:34 Go to previous messageGo to next message
Matt Haffner is currently offline  Matt Haffner
Messages: 34
Registered: October 2000
Member
You don't have to download a version from the Eclipse website. They switched the "Workbench" to Eclipse in v7. Just run the IDLDE application and you'll be using Eclipse with the IDL extensions. It's specifically customized for IDL coding/debugging.

If you get interested in using Eclipse for other coding, I'd recommend downloading the Eclipse for C developers and add language modules as needed. It's a version or so ahead of the Eclipse used for IDL.

- Matt

On Wednesday, June 12, 2013 9:02:04 AM UTC-5, AMS wrote:
> Hi Fabien,
>
>
>
> Thanks for the info; auto-indent and so on are nice features. So maybe I should swap to that on the Windows machine.
>
>
>
> But which download from these fourteen is the basic text editor I'd want to use? http://www.eclipse.org/downloads/ And is the IDL highlighter included?
>
>
>
> I thought maybe this one, although the page doesn't explain too much what is there: http://www.eclipse.org/downloads/packages/eclipse-classic-42 2/junosr2
>
>
>
> (Note I don't use Workbench or anything, I compile/run from command line, and also only code in IDL/Fortan/C so don't need bells and whistles or things for other languages.)
>
>
>
> Thanks (and sorry for the threadjacking),
>
>
>
> Andy
>
>
>
> On Wednesday, June 12, 2013 9:53:13 AM UTC-4, Fabien wrote:
>
>> Hi Andy,
>
>>
>
>>
>
>>
>
>> On 06/12/2013 03:37 PM, AMS wrote:
>
>>
>
>>> what is it about Eclipse that means I would want to use it instead?
>
>>
>
>>
>
>>
>
>> Sure, it's a valid question.
>
>>
>
>>
>
>>
>
>> The first argument that comes to mind is that IDL (since V7) is using
>
>>
>
>> eclipse as out-of-the-box workbench. That means that (at least) a few
>
>>
>
>> people are thinking about how to integrate best the IDL features into
>
>>
>
>> the workbench (I hope so;-)).
>
>>
>
>>
>
>>
>
>> Second, Eclipse is Open Source and has been developed and used for many
>
>>
>
>> many other languages, so it is well known and still an active project.
>
>>
>
>> It is organized in "views" and "projects" and supports SVN (usually very
>
>>
>
>> easily but with IDL it is sometimes a pain :()
>
>>
>
>>
>
>>
>
>> Third, (this is where your own habits or tastes comes into the game), it
>
>>
>
>> has cool features and shortcuts. I like how fast I can navigate in the
>
>>
>
>> code using CTRL+F3 for example, I like auto-completion (CTRL+Space), I
>
>>
>
>> like the auto-indenting (CTRL+SHIFT+F), and many other small things.
>
>>
>
>> What Eclipse doesn't have is Emacs-Style programming (not to my
>
>>
>
>> knowledge, but possibly someone made something similar happen in eclipse
>
>>
>
>> too)
>
>>
>
>>
>
>>
>
>> The third point is where other people might find it faster to use
>
>>
>
>> another editor... But I always wonder why, so I am asking ;-)
>
>>
>
>>
>
>>
>
>> Cheers,
>
>>
>
>>
>
>>
>
>> Fab
Re: function/procedure/keyword list for use in creating an editor syntax description [message #84846 is a reply to message #84839] Thu, 13 June 2013 06:06 Go to previous message
Andy Sayer is currently offline  Andy Sayer
Messages: 127
Registered: February 2009
Senior Member
Thanks for the suggestion; I don't use the Workbench/IDLDE for any coding though. I use a text editor and then run code via command line.

(I'm typically running code on multiple remote machines using different OSs and find it easier to open terminals and do it that way, than use IDLDE. Of course last time I used IDLDE was version 6 or something so it may be different now.)

On Wednesday, June 12, 2013 6:34:38 PM UTC-4, Matt Haffner wrote:
> You don't have to download a version from the Eclipse website. They switched the "Workbench" to Eclipse in v7. Just run the IDLDE application and you'll be using Eclipse with the IDL extensions. It's specifically customized for IDL coding/debugging.
>
>
>
> If you get interested in using Eclipse for other coding, I'd recommend downloading the Eclipse for C developers and add language modules as needed. It's a version or so ahead of the Eclipse used for IDL.
>
>
>
> - Matt
>
>
>
> On Wednesday, June 12, 2013 9:02:04 AM UTC-5, AMS wrote:
>
>> Hi Fabien,
>
>>
>
>>
>
>>
>
>> Thanks for the info; auto-indent and so on are nice features. So maybe I should swap to that on the Windows machine.
>
>>
>
>>
>
>>
>
>> But which download from these fourteen is the basic text editor I'd want to use? http://www.eclipse.org/downloads/ And is the IDL highlighter included?
>
>>
>
>>
>
>>
>
>> I thought maybe this one, although the page doesn't explain too much what is there: http://www.eclipse.org/downloads/packages/eclipse-classic-42 2/junosr2
>
>>
>
>>
>
>>
>
>> (Note I don't use Workbench or anything, I compile/run from command line, and also only code in IDL/Fortan/C so don't need bells and whistles or things for other languages.)
>
>>
>
>>
>
>>
>
>> Thanks (and sorry for the threadjacking),
>
>>
>
>>
>
>>
>
>> Andy
>
>>
>
>>
>
>>
>
>> On Wednesday, June 12, 2013 9:53:13 AM UTC-4, Fabien wrote:
>
>>
>
>>> Hi Andy,
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> On 06/12/2013 03:37 PM, AMS wrote:
>
>>
>
>>>
>
>>
>
>>>> what is it about Eclipse that means I would want to use it instead?
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> Sure, it's a valid question.
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> The first argument that comes to mind is that IDL (since V7) is using
>
>>
>
>>>
>
>>
>
>>> eclipse as out-of-the-box workbench. That means that (at least) a few
>
>>
>
>>>
>
>>
>
>>> people are thinking about how to integrate best the IDL features into
>
>>
>
>>>
>
>>
>
>>> the workbench (I hope so;-)).
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> Second, Eclipse is Open Source and has been developed and used for many
>
>>
>
>>>
>
>>
>
>>> many other languages, so it is well known and still an active project.
>
>>
>
>>>
>
>>
>
>>> It is organized in "views" and "projects" and supports SVN (usually very
>
>>
>
>>>
>
>>
>
>>> easily but with IDL it is sometimes a pain :()
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> Third, (this is where your own habits or tastes comes into the game), it
>
>>
>
>>>
>
>>
>
>>> has cool features and shortcuts. I like how fast I can navigate in the
>
>>
>
>>>
>
>>
>
>>> code using CTRL+F3 for example, I like auto-completion (CTRL+Space), I
>
>>
>
>>>
>
>>
>
>>> like the auto-indenting (CTRL+SHIFT+F), and many other small things.
>
>>
>
>>>
>
>>
>
>>> What Eclipse doesn't have is Emacs-Style programming (not to my
>
>>
>
>>>
>
>>
>
>>> knowledge, but possibly someone made something similar happen in eclipse
>
>>
>
>>>
>
>>
>
>>> too)
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> The third point is where other people might find it faster to use
>
>>
>
>>>
>
>>
>
>>> another editor... But I always wonder why, so I am asking ;-)
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> Cheers,
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>>
>
>>
>
>>> Fab
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: dialog_pickfile - multiple directories
Next Topic: time range

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 13:34:08 PDT 2025

Total time taken to generate the page: 0.00687 seconds