If you make it a log thingy, you can enable logs on a per-class basis.
Something like
lzc -lorg.openlaszlo.compiler.Parser=debug
On 2007-03-31, at 21:16 EDT, Henry Minsky wrote:
To start with you can add this line to Parser.java, and then when
you run
lzc it will print to the console
$ svn diff WEB-INF/lps/server/src/org/openlaszlo/compiler/Parser.java
Index: WEB-INF/lps/server/src/org/openlaszlo/compiler/Parser.java
===================================================================
--- WEB-INF/lps/server/src/org/openlaszlo/compiler/Parser.java
(revision
4555)
+++ WEB-INF/lps/server/src/org/openlaszlo/compiler/Parser.java
(working
copy)
@@ -440,6 +440,12 @@
Parser.class.getName(),"051018-438")
, child);
}
+
+ System.err.println(href + " included by " +
+
getUserPathname(getSourcePathname(element)) + ":"+
+ getSourceLocation(child, LINENO));
+
+
File target = resolver.resolve(href, base);
// An include whose href is a directory implicitly
// includes the library.lzx file in that directory.
And then it will print to the console when you run lzc
On 3/31/07, Sarah Allen <[EMAIL PROTECTED]> wrote:
I just wrote up this feature request:
LPP-3815 Debugging tool that will tell me what files are included by
what
I don't know if the size profiler would be the right spot for
this. But
when you have a big app and you are trying to make it smaller, it is
really time consuming to find where the extra stuff is added in. I'd
settle for debug output from lzc.
I'll bet this would be easy for someone who knows the compiler.
Who can
I bribe to whip up a change to 3.4 that will let me see this
info? I'll
buy beers the next time you are in SF, or the beverage of your
choice.
Or at least, maybe someone could point me to the place in the code
where
I could make this change.
Thanks!
Sarah
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
