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

Home » Public Forums » archive » "$Id:" field at top of procedure
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
"$Id:" field at top of procedure [message #89481] Mon, 20 October 2014 14:15 Go to next message
rmp116 is currently offline  rmp116
Messages: 3
Registered: October 2014
Junior Member
Hi all,

My apologies in advance for the very simple question, but I just can't find an answer anywhere else. What does the "$Id:" at the top of an IDL procedure do?

Thanks,
Robert
Re: "$Id:" field at top of procedure [message #89483 is a reply to message #89481] Mon, 20 October 2014 14:31 Go to previous messageGo to next message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
rmp116@gmail.com writes:

> My apologies in advance for the very simple question, but I just can't find an answer anywhere else. What does the "$Id:" at the top of an IDL procedure do?

It identifies the version of the file that was checked out of the
version control system. It is probably of no interest to you and you can
just ignore it. It would be of great interest to someone who was trying
to fix a problem with the file.

Cheers,

David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
Re: "$Id:" field at top of procedure [message #89484 is a reply to message #89481] Mon, 20 October 2014 14:32 Go to previous messageGo to next message
Craig Markwardt is currently offline  Craig Markwardt
Messages: 1869
Registered: November 1996
Senior Member
On Monday, October 20, 2014 5:15:33 PM UTC-4, rmp...@gmail.com wrote:
>
> My apologies in advance for the very simple question, but I just can't find an answer anywhere else. What does the "$Id:" at the top of an IDL procedure do?


Good question. It doesn't "do" anything. It's purely informational for developers.

That's a string used by developers to track versions of software as they are developed and checked in to a code respository. The ID portion uniquely identifies a revision. Programs like CVS or SVN insert the version information automatically. If you are writing your own IDL code, you do not need to use an Id at all.

Craig
Re: "$Id:" field at top of procedure [message #89485 is a reply to message #89481] Mon, 20 October 2014 14:54 Go to previous messageGo to next message
rmp116 is currently offline  rmp116
Messages: 3
Registered: October 2014
Junior Member
On Monday, October 20, 2014 11:15:33 AM UTC-10, rmp...@gmail.com wrote:
> Hi all,
>
>
>
> My apologies in advance for the very simple question, but I just can't find an answer anywhere else. What does the "$Id:" at the top of an IDL procedure do?
>
>
>
> Thanks,
>
> Robert

Thank you both! That's been bugging me for a while.

Robert
Re: "$Id:" field at top of procedure [message #89503 is a reply to message #89481] Wed, 22 October 2014 09:24 Go to previous message
Paul Van Delst[1] is currently offline  Paul Van Delst[1]
Messages: 1157
Registered: April 2002
Senior Member
On 10/20/14 17:15, rmp116@gmail.com wrote:
> Hi all,
>
> My apologies in advance for the very simple question, but I just
> can't find an answer anywhere else. What does the "$Id:" at the top
> of an IDL procedure do?

Others have answered. Here's the link to how subversion documents the
"standard" keyword substitution.
http://svnbook.red-bean.com/en/1.7/svn.advanced.props.specia l.keywords.html

cheers,

paulv

p.s. And yes, it's very handy (to folks that distribute code) to allow
the tracking down of *exactly* what revision of a file is causing problems.
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: save contour to eps in 8.2.3
Next Topic: Plotting Seasons

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

Current Time: Wed Oct 08 13:32:37 PDT 2025

Total time taken to generate the page: 0.00588 seconds