title: Why do we need Application.PathSeparator?
body: <p><strong>MS Office VBA has a property called <a href="https://msdn.microsoft.com/en-us/vba/excel-vba/articles/application-pathseparator-property-excel" rel="nofollow noreferrer"></strong><code>Application.PathSeparator</code><strong></a>.</strong></p>
  
  <p>I'm supportive of <a href="https://en.wikipedia.org/wiki/Interoperability" rel="nofollow noreferrer" title="in·ter·op·er·a·bil·i·ty → &#13;the ability of computer systems or software to exchange and make use of information.">interoperability</a>, but Office runs <a href="https://en.wikipedia.org/wiki/Microsoft_Office#Platforms" rel="nofollow noreferrer">only</a> on Windows &amp; MacOS, and both platforms use <a href="https://en.wikipedia.org/wiki/Path_(computing)#Representations_of_paths_by_operating_system_and_shell" rel="nofollow noreferrer">the same</a> <code>\</code> path separator.</p>
  
  <p><strong>When would it <em>ever</em> be advisable to use <code>Application.PathSeparator</code></strong> (as opposed to simply hardcoding the <code>\</code> and saving 22 keystrokes)?</p>
  
  <hr>
  
  <p>To be clear, I <strong>do</strong> think it's important to support international differences when posting code on an <a href="https://insights.stackoverflow.com/survey/2018/#geography" rel="nofollow noreferrer">international site like Stack Overflow</a>, so I will often use <code>Application.International</code> properties such as <code>xlDateSeparator</code> and, more importantly, <code>xlDateOrder</code>. <sub>(More about those <a href="https://msdn.microsoft.com/en-us/vba/excel-vba/articles/application-international-property-excel" rel="nofollow noreferrer">here</a>)</sub></p>