comp.lang.idl-pvwave archive: archive » Re: Name Space Conflicts

Home » Public Forums » archive » Re: Name Space Conflicts

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

Re: Name Space Conflicts [message #47975 is a reply to message #47864]

Thu, 09 March 2006 08:41

Tom Berger
Messages: 2
Registered: March 2006

Junior Member

How about something analogous to cryptography where you have a
"namespace key" set in an environment variable or on the command line
that IDL checks before compiling a routine. This "public namespace key"
changes depending on which application you're working on. Then, inside
those routines that should be compiled with a given application there's
a uniquely defined "routine key" that fits with the namespace,
something like a C-code pragma instruction mechanism. If the compiler
doesn't find a matching key, it stops compilation and examines the next
instance of IMGSCL that it finds, continuing until a match is found at
which point it fully compiles the code. This would necessitate going
back into all of your routines and assigning these uniques keys, but
that could be automated pretty easily. This is just thinking out loud
- it could be completely stupid. But it seems like there needs to be
"another level" of namespace checking that goes on besides the brute
force !PATH method.

Report message to a moderator

[Message index]

		Re: Name Space Conflicts By: Paul Van Delst[1] on Wed, 08 March 2006 13:17
		Re: Name Space Conflicts By: David Fanning on Wed, 08 March 2006 12:49
		Re: Name Space Conflicts By: Paul Van Delst[1] on Wed, 08 March 2006 12:34
		Re: Name Space Conflicts By: Tom Berger on Thu, 09 March 2006 08:41

Previous Topic:	Problems with Restore
Next Topic:	Processing getting slower and slower?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 06:19:07 PDT 2025

Total time taken to generate the page: 1.27926 seconds