How to prevent duplicate include?

[d.healey]

@aaronventure I only put includes directly in on init to avoid this issue.

[aaronventure]

@d-healey

what do you mean? Where else would one put them? I get an error "Duplicate namespace" nonetheless.

[d.healey]

@aaronventure said in How to prevent duplicate include?:

Where else would one put them?

Ah I thought you meant you were attempting to include them within another namespace.

@aaronventure said in How to prevent duplicate include?:

"Duplicate namespace"

That means you have two namespaces with the same name, so change the name of one of them.

[aaronventure]

@d-healey Alright here's an example.

I have Animation.js which also relies on MathX.js

I don't want to have t remember that, so if I load in Animation.js after I alreaded included MathX.js, the Animation.js should skip its own include for the MathX,js .

This can be done with the preprocessor, but the preprocessor constants are global so I can't do the same trick in another script processor.

The include call does not respect HISEScript's if/then -- I can't declare a HISEScript const inside the include file that I can then check for using if/then.

[d.healey]

@aaronventure said in How to prevent duplicate include?:

Animation.js should skip its own include for the MathX,js .

This is what I mean by I put all my includes directly in on init not within another script file. That way I have to explicitly state what includes are available, the worst that happens is when I include a file it tells me that it can't find X function/namespace so I have to add another include.

[ustk]

@aaronventure Haven't tried, but you could start all your namespaces with a variable of the same name, and check isDefined(MyNamespace.MyVar) in dependencies. If not defined just throw a message in the console for which include is required.
It's far from being automated but at least you get all the required includes at init showing in the console.

A use of Console.assert might be helpful as well in the include's functions that depend on others includes/namespaces

[aaronventure]

@ustk yep that's what I'll do, thanks

[d.healey]

@aaronventure I'm seeing a good use case for this in my latest project. I tried @ustk suggestion but it didn't work. Did you find a solution?

[aaronventure]

@d-healey Yeah, for each namespace, I have a exists constant.

Then in the ones that require other namespaces, I have, for example

if (MathX.exists == false)
	{
		Console.print("Controls.js requires MathX.");
	}

[d.healey]

@aaronventure ah I get it now, thanks.

[d.healey]

@Christoph-Hart What about adding #pragma once? Or just ignoring duplicate includes - I can't think of a downside to that but maybe there is.