comp.lang.idl-pvwave archive: archive » Re: How to specify which exact version of a subroutine to use....

Home » Public Forums » archive » Re: How to specify which exact version of a subroutine to use....

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: How to specify which exact version of a subroutine to use.... [message #75546 is a reply to message #75545]

Thu, 17 March 2011 13:26

penteado
Messages: 866
Registered: February 2018

Senior Member
Administrator

On Mar 17, 1:44 pm, David Fanning <n...@idlcoyote.com> wrote:
> And if you DO make changes to someone else's library
> programs and choose not to tell them about it, at least
> give the programs a different name. Otherwise chaos will
> reign supreme. :-(

Anytime I change someone elses's code I add a _pp suffix to the name.
Besides making it a different name, it is also not the same identifier
to the routines I write (for those I use a pp_ prefix), and it makes
the edited routine follow the original alphabetically.

Report message to a moderator

[Message index]

		Re: How to specify which exact version of a subroutine to use.... By: penteado on Thu, 17 March 2011 13:30
		Re: How to specify which exact version of a subroutine to use.... By: penteado on Thu, 17 March 2011 13:26
		Re: How to specify which exact version of a subroutine to use.... By: David Fanning on Thu, 17 March 2011 12:42
		Re: How to specify which exact version of a subroutine to use.... By: George Millward on Thu, 17 March 2011 12:26
		Re: How to specify which exact version of a subroutine to use.... By: pgrigis on Thu, 17 March 2011 10:39
		Re: How to specify which exact version of a subroutine to use.... By: David Fanning on Thu, 17 March 2011 09:44
		Re: How to specify which exact version of a subroutine to use.... By: David Fanning on Thu, 17 March 2011 09:40

Previous Topic:	Re: CG resizable window won't resize during read
Next Topic:	IDL Book Tour

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 14:53:43 PDT 2025

Total time taken to generate the page: 1.76074 seconds