From 5e1a0052523349775be1cc98b4094c44804f1240 Mon Sep 17 00:00:00 2001 From: Eugene Burmako Date: Tue, 24 Jul 2012 12:14:54 +0200 Subject: removes -Xmacro-(.*)-classpath compiler options These options were meant to be used to bootstrap macros defined in our codebase However we can bootstrap perfectly without any additional effort, because library classpath classloader can delegate to tool classpath classloader to load macro implementations from starr. Since then (for several months) this functionality hasn't proven to be useful, neither anyone on the mailing list or stackoverflow asked questions about it (even despite it was explicitly mentioned in the "cannot load macro impl" error message). Hence I suggest that it is totally unnecessary and should be removed. --- test/files/neg/macro-basic-mamdmi.check | 1 - 1 file changed, 1 deletion(-) (limited to 'test/files/neg/macro-basic-mamdmi.check') diff --git a/test/files/neg/macro-basic-mamdmi.check b/test/files/neg/macro-basic-mamdmi.check index eef444f7b3..67b00c0ec5 100644 --- a/test/files/neg/macro-basic-mamdmi.check +++ b/test/files/neg/macro-basic-mamdmi.check @@ -1,5 +1,4 @@ Impls_Macros_Test_1.scala:36: error: macro implementation not found: foo (the most common reason for that is that you cannot use macro implementations in the same compilation run that defines them) -if you do need to define macro implementations along with the rest of your program, consider two-phase compilation with -Xmacro-fallback-classpath in the second phase pointing to the output of the first phase println(foo(2) + Macros.bar(2) * new Macros().quux(4)) ^ one error found -- cgit v1.2.3