Preprocessing identifier Conditional attribute

Hey there,

I am using some compiler conditionals with platforms and saw in the documentation here that you can use the Conditional attribute like this. I can not seem to get it to work though, if I put it before the function it still compiles.

for example:

Code (csharp):

1.  
2.         [System.Diagnostics.Conditional("UNITY_ANDROID")]
3.         static void Test(string fileName)
4.         {
5.             string filePath = Application.persistentDataPath + "/" + fileName;
6.             WWW load = new WWW("test");
7.             System.IO.File.WriteAllBytes(filePath, load.bytes);
8.         }
9.  

Gives the error for the WriteAllBytes function when in web build mode in the editor

but this does work while in web platform in the editor without editors like it should

Code (csharp):

1.  
2. #if UNITY_ANDROID
3.         static void Test(string fileName)
4.         {
5.             string filePath = Application.persistentDataPath + "/" + fileName;
6.             WWW load = new WWW("test");
7.             System.IO.File.WriteAllBytes(filePath, load.bytes);
8.         }
9. #endif
10.  

Am I doing something wrong here?

 

Yeah, it looks like the ConditionalAttribute only works for custom defines. It works as expected with my own defines, but when it comes to standard platform symbols like "UNITY_EDITOR", I have no luck neither. Kind of a bummer.

 

I just realized after reading this: http://stackoverflow.com/questions/3788605/if-debug-vs-conditionaldebug that it's actually expected behaviour. You see, only calls are stripped, but methods are still compiled into IL. And at this point your System.IO.File.WriteAllBytes() simply doesn't exist. It doesn't matter that the method is never going to be called in the resulting code. The compiler doesn't know. Still a bummer though.

 

By the way, the solution is obvious (for anyone who reads this later). Just wrap the inside of the problematic method in #if directive like this:

Code (CSharp):

1. [System.Diagnostics.Conditional("UNITY_ANDROID")]
2. static void Test(string fileName)
3. {
4. #if UNITY_ANDROID
5.        string filePath = Application.persistentDataPath + "/" + fileName;
6.        WWW load = new WWW("test");
7.        System.IO.File.WriteAllBytes(filePath, load.bytes);
8. #endif
9. }
10.  

And you can call Test() anywhere else without worries.

 

In this case the `Conditional` attribute looses the purpose

 

Not really, it saves you the overhead of calling an empty method when the platform, in this specific example, isn't android.

 

No, maybe your understanding is wrong for the "purpose of conditional attribute" or you only need the preprocessor define.

The conditional attribute has no effect on the callee side, it works on the caller side.

The code for the method will compile and will be included in the IL level, however, calls to the method will be omitted if the preprocessor define is not set on the caller side.

TLDR:

If you do not want the code to compile to the IL use the following:

Code (CSharp):

1. #if UNITY_ANDROID
2.     //----
3. #endif

If you want the code to compile to the IL but execute it in some places and not execute it in other places conditionally use the following:

Code (CSharp):

1. [System.Diagnostics.Conditional("UNITY_ANDROID")]

 

Yeah, that defies the purpose.
Now you have to pepper #ifdefs throughout your code.
It could, COMPLETELY LEGALLY, compile, and then be stripped on the IL level.
But no. We cannot have nice things.
(or, you know, UnityEditor could just be a stub Assembly for builds)
(especially in ECS baking, this is so densely mixed, and you can't just put your Authoring Behaviours into Editor folders, because Unity made that Maliciously illegal as well - can't have editor scripts on game objects, even though there are about a dozen very concrete use cases for them)