<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 2/23/23 1:06 PM, Archie Cobbs wrote:<br>
</div>
<blockquote type="cite" cite="mid:CANSoFxum7aFO=DKOmYbE49i_HWs=+xHgGYo0L79agF3fBXrhrQ@mail.gmail.com">
<div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div>
<p><br>
</p>
</div>
</div>
</div>
</blockquote>
<p>If anyone were to pursue this, I would recommend that
it be done at least 99.99% in a separate implementation
of `java.nio.file.FileSystem`, and not directly in
javac itself. Such a FileSystem could be used without
changing javac at all when invoking javac through its
API (i.e. `javax.tools.JavaCompiler.getTask`), or with
minimal change to command-line javac to specify the use
of that file system.</p>
</div>
</blockquote>
<div>That's a neat approach.</div>
<div><br>
</div>
<div>The idea of a javac flag like <span style="font-family:monospace">--use-filesystem-impl
com.foobar.MyFileSystem</span> is something that could be
useful in its own right.<br>
</div>
</div>
<br clear="all">
</div>
<div>-Archie</div>
</blockquote>
<p>FWIW, I probably meant `javax.tools.JavaFileManager` instead of
`java.nio.file.FileSystem`. That good, because it's easier to
write an interposing file manager than a new file system. :-)</p>
<p>-- Jon<br>
</p>
<p><br>
</p>
</body>
</html>