Specifying the charset to the compiler

Hi!
I got a weird problem. I'm building a java system with eclipse, and when I compile se sources with the eclipse built-in compiler, everything works fine, but when I compile directly with javac, all my ISO-8859-1 characters are lost!
There is a way of telling the compiler the charset to be used? anyone knows what is happening?
Thanks!

When I type only "javac" at the command line, it gives me a list of options I can use. One of them is "-encoding"... doesn't yours give you that option?

Similar Messages

Error while executing the compilation process

Hi,
ISA Framework: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: javac: invalid flag: "/usr/sap/CJP/J06/j2ee/cluster/server2/apps/sap.com/crm~isauseradm/servlet_jsp/isauseradm/work/jsp_login XXXXXXXXXXX.java" Usage: javac <options> <source files> where possible options include: -g Generate all debugging info -g:none Generate no debugging info -g:{lines,vars,source} Generate only some debugging info -nowarn Generate no warnings -verbose Output messages about what the compiler is doing -deprecation Output source locations where deprecated APIs are used -classpath <path> Specify where to find user class files -sourcepath <path> Specify where to find input source files -bootclasspath <path> Override location of bootstrap class files -extdirs <dirs> Override location of installed extensions -d <directory> Specify where to place generated class files -encoding <encoding> Specify character encoding used by source files -source <release> Provide source compatibility with specified release -target <release> Generate class files for specific VM version -help Print a synopsis of standard options ].
We get this message periodically then we login to isauseradm-application or shopadmin-application.
How we can solve this issue? Why it's appears in system?
/nwa shows this error:
Process after commit failed - may be hanging internal locks mut be removed manually.
Where I can see hanging internal locks ?
Denis

to add some information,
in runtime workbench, component monitoring, performance monitoring and all other thing except message monitoring is OK.

Specify the GUI declaratively in ActionScript like in JavaFX Script instead of MXML

After reading a bit about JavaFX Script (which is actually remarkebly close to ActionScript 3) as a developer I thought the way one can specify the GUI declaratively in JavaFX Script via JSON-like notation for the components is pretty cool. It would be nice to have something like that in Flex/ActionScript too. The advantages I see over MXML are:
1) a more compact notation than XML which is nice from a developers view point who actually writes this kind of code. Of course the idea would be that designers still design the GUI with graphical tools that generate this code but if you have to dive in and edit the code it's nice not to have to deal with verbose XML and I think even designers can easily understand JSON-like code; don't just assume that designers love XML because HTML was based on SGML! I'm not so sure if today many designers really still know raw HTML that well (like in 1997, the early days...). Server side developers probably know it better because they have to adapt it to jsp or asp or whatever framework.
2) The fact that it's all ActionScript gives a seamless integration between just composing the components to form the GUI and adding scripts to add additionial behavior instead of mixing XML with actionscript code => no more need for those nasty CDATA blocks! It would also be easy for development tools like Flexbuilder to give a seamsless experience with code completion and zooming in on the code because it's all Actionscript! There's also no need for a separate expression language to tie the MXML to the underlying Actionscript. It would it also make easier to create custom components (not just simple composition components which is really easy in MXML) because you don't have to implement separate XML tags.
here's a short JavaFX Script example:
Frame {
content: GroupPanel {
var myRow = Row { alignment: BASELINE }
var label_col = Column { alignment: TRAILING }
var field_col = Column { alignment: LEADING }
rows: [myRow]
columns: [label_col, field_col]
content:
[SimpleLabel {
row: myRow
column: label_col
text: "Type your text here:"
TextField {
row: myRow
column: field_col
columns: 50
visible: true
Note that this shouldn't be confused with programmatically specifying the GUI in Actionscript (which is possible today as an alternative to MXML). What I propose is at a (slightly) higher level: you don't give a detailed sequence of methods/functions to call to construct the GUI (i.e. HOW to do it) but just specify WHAT you want.
Hopefully some Adobe Flex will see this and think about it. Although I think MXML is not too bad and I can live with it if I have to ;)

I like that idea Sean. A standard and well-supported way to separate MXML and code would be good. I'd love to have builder support a MVC style triad for MXML files, with the
model.as being simply an all-public-all-bindable class full of VOs and view-specific information, any view-manipulation and view<->app communications in the
controller.as, and nothing but bindings and layour in the MXML. There's (almost) nothing stopping you doing this by hand at the moment, but it's a pain, and developers wouldn't stick to it for very long, when they need to create and maintain 3 separate files for that simple "error dialog" without a hand from Builder.
Then again, I'd rather Adobe spent the time that would take on opening and better-documenting builder's APIs, so we can write our own plugins easily, but that's my greedy side- A standard builder-supported MVC pattern for custom MXML components would be aweseome for people that aren't me :)
-Josh
As for JavaFX, I don't care for it.
On Tue, Sep 30, 2008 at 7:56 AM, Sean Christmann
<
[email protected]> wrote:
A new message was posted by Sean Christmann in
Developers --
  specify the GUI declaratively in ActionScript like in JavaFX Script instead of MXML
Jason you bring up a good point on a concept that I think Adobe should
poach from a different framework, Silverlight. In Silverlight the
code-behind pattern is automatic and very nice to work with. Every
interface can be composed of both a layout file and a script file, and
they get composited into the SAME class at compile time. So you can
have both a FileDialog.mxml and FileDialog.as file that know about each
other automatically, without the need to subclass one from the other.
Sean
Jason Stafford wrote:
A new message was posted by Jason Stafford in
Developers --
specify the GUI declaratively in ActionScript like in JavaFX Script instead of MXML
Personally, I like the separation between the MXML and ActionScript.
We're working on a large project, and so we have all the ActionScript
separate from the MXML files. For example we'll have something like
filedialoglayout.mxml, and then
filedialog.as that is a subclass of
filedialoglayout. All event handlers and the like are setup in the
filedialog.as file - the mxml file doesn't know about any function names.
Advantages:
MXML files become layout only - and are more easily shared and worked on
with non-technical people
ActionScript is all in *.as files: no CDATA blocks and no FlexBuilder
quirks where editing ActionScript inside a CDATA block doesn't work
quite like in a real AS file.
For simple experiments, and for learning, it's obviously nice to have
everything in one mxml file, but in a big project like ours, the
separation helps keep things clearer and more maintainable.
Why use the mxml at all? The MXML files are nice to edit with the
visual editor in Flex Builder, and it's much easier to apply styles and
embed assets in MXML than it is in pure ActionScript.
I think two ways to talk about the same thing (XML and ActionScript) is
already almost one too many - adding a third (JSON) would really be too
much.
Just my thoughts.
-Jason Stafford
Sean Christmann wrote:
A new message was posted by Sean Christmann in
Developers --
specify the GUI declaratively in ActionScript like in JavaFX Script
instead of MXML
This reminds me of a certain workflow pattern that has emerged for us
which might help provide some insight on this topic. I'm working on a
project with a couple other developers which connects to a webservice
for supplying clientside data. This data is available in both json
notation and xml notation. The thing is, while the developers have
overwhelmingly agreed that we should be consuming the json version
since it can be parsed faster and provide more meaningful context for
objects (ie strings vs ints vs arrays etc...), all these same
developers rely exclusively on the xml notation when asking questions
about the data or passing structures around to discuss.
I see the same thing when looking at JavaFX and MXML. JavaFX might
allow for more accurate structures and might be able to be compiled
faster, but MXML is better for being self documenting even if it
requires more verbosity.
Sean
Matt Chotin wrote:
A new message was posted by Matt Chotin in
Developers --
specify the GUI declaratively in ActionScript like in JavaFX Script
instead of MXML
I'd be curious what other people think. I see MXML as a distinct
advantage over doing the pseudo-script stuff. I really don't like
the JavaFX system actually.
Matt
On 9/28/08 10:33 AM, "neo7471"
<[email protected]> wrote:
A new discussion was started by neo7471 in
Developers --
specify the GUI declaratively in ActionScript like in JavaFX Script
instead of MXML
After reading a bit about JavaFX Script (which is actually remarkebly
close to ActionScript 3) as a developer I thought the way one can
specify the GUI declaratively in JavaFX Script via JSON-like notation
for the components is pretty cool. It would be nice to have something
like that in Flex/ActionScript too. The advantages I see over MXML are:
1) a more compact notation than XML which is nice from a developers
view point who actually writes this kind of code. Of course the idea
would be that designers still design the GUI with graphical tools
that generate this code but if you have to dive in and edit the code
it's nice not to have to deal with verbose XML and I think even
designers can easily understand JSON-like code; don't just assume
that designers love XML because HTML was based on SGML! I'm not so
sure if today many designers really still know raw HTML that well
(like in the 1997, the early days...). Server side developers
probably know it better because they! have to adapt it to jsp or asp
or whatever framework.
2) The fact that it's all ActionScript gives a seamless integration
between just composing the components to form the GUI and adding
scripts to add additionial behavior instead of mixing XML with
actionscript code => no more need for those naster CDATA blocks! It
would also be easy for development tools like Flexbuilder to give a
seamsless experience with code completion and zooming in on the code
because it's all Actionscript! There's also no need for a separate
expression language to tie the MXML to the underlying Actionscript.
It would it also make easier to create custom components (not just
simple composition components which is really easy in MXML) because
you don't have to implement separate XML tags.
here's a short JavaFX Script example:
Frame {
    content: GroupPanel {
    var myRow = Row { alignment: BASELINE }
    var label_col = Column { alignment: TRAILING }
    var field_col = Column { alignment: LEADING }
    rows: [myRow]
    columns: [label_col, field_col]
    content:
    [SimpleLabel {
    row: myRow
    column: label_col
    text: "Type your text here:"
    TextField {
    row: myRow
    column: field_col
    columns: 50
    visible: true
Note that this shouldn't be confused with programmatically specifying
the GUI in Actionscript (which is possible today as an alternative to
MXML). What I propose is at a (slightly) higher level: you don't give
a detailed sequence of methods/functions to call to construct the GUI
(i.e. HOW to do it) but just specify WHAT you want.
Hopefully some Adobe Flex will see this and think about it. Although
I think MXML is not too bad and I can live with it if I have to ;)
View/reply at specify the GUI declaratively in ActionScript like in
JavaFX Script instead of MXML
<
http://www.adobeforums.com/webx?13@@.59b69b42>
Replies by email are OK.
Use the unsubscribe
<
http://www.adobeforums.com/webx?280@@.59b69b42!folder=.3c060fa3>
form to cancel your email subscription.
View/reply at
<
http://www.adobeforums.com/webx?13@@.59b69b42/0>
Replies by email are OK.
Use the unsubscribe form at
<
http://www.adobeforums.com/webx?280@@.59b69b42!folder=.3c060fa3> to
cancel your email subscription.
<div><div></div><div>
Jason Stafford
Principal Developer
Inspiration Software, Inc.
The leader in visual thinking & learning
Now available - Kidspiration(r) 3, the visual way to explore and understand words, numbers and concepts.
Learn more at
www.inspiration.com/kidspiration.
503-297-3004 Extension 119
503-297-4676 (Fax)
9400 SW Beaverton-Hillsdale Highway
Suite 300
Beaverton, OR 97005-3300
View/reply at
<
http://www.adobeforums.com/webx?13@@.59b69b42/2>
Replies by email are OK.
Use the unsubscribe form at
<
http://www.adobeforums.com/webx?280@@.59b69b42!folder=.3c060fa3></div>
</div> to cancel your email subscription.
Sean Christmann | Experience Architect | EffectiveUI | 720.937.2696
View/reply at
specify the GUI declaratively in ActionScript like in JavaFX Script instead of MXML
Replies by email are OK.
Use the
unsubscribe form to cancel your email subscription.
"Therefore, send not to know For whom the bell tolls. It tolls for thee."
http://flex.joshmcdonald.info/
:: Josh 'G-Funk' McDonald
:: 0437 221 380 ::
[email protected]

Specify the full package path

Well, here is a real beginner question. How can i specify the full package path of SUNs java.io package? And another beginner question, where is this package located on my computer? (relative to my java sdk installion path of course)

Acctually I have a severe problem with leJOS. Here is my code:
import java.io.*;
import josx.rcxcomm.RCXBean;
public class PCModule
     public static void main( String[] args )
          recv();
     public static void recv()
          RCXBean rcxb = new RCXBean();
          try
               rcxb.setComPort("USB");
               while(true)
                    System.out.println( "Test" );
          catch( IOException e )
}This should compile fine, if lejosc would use the SUN java.io But it intends to use the own implementation of java.io and I really need to find a workaround to this problem because otherwise the code wont compile throwing the error, that the out symbol cannot be resolved.
Btw. this part of the program should listen to the mindstorms IR-Tower for messages of a RCX-Brig and wirte them to an output stream.
Isn't there a way to force lejosc to use the java.io package from sun?
P.S.: If I don't use the System.out-line everything is fine, so lejos is installed correctly and if write a java test app everything is fine, so the SUN Java SDK is installed correctly too.

How do I specify the Startup VI for a LLB in LV 8.5.1 Full?

Hi,
I recently upgraded to LabVIEW 8.5.1 from LabVIEW 7.1.1. I entered the project Build Specifications and compiled my code into a LV .llb file called "my_program.llb". I also specified the top level vi (called "main.vi") inside my_program.llb. Now I want to make "main.vi" automatically open and execute whenever the user double clicks on my_program.llb from within Windows Explorer. How can I do this in LV 8.5.1 Full?
Right now when the user double clicks on my_program.llb, the LLB Manager window opens, but "main.vi" doesn't automatically launch like it used to do back when I was using LabVIEW 7.1.1 Full.
I know it is possible to specify the Startup VI using the Professional version, but is this possible to do in the Full version?
Thanks,
Richard
Solved!
Go to Solution.

Check out this KB
Managing LabVIEW Library Files in Windows Explorer & the LLB Manager
LabVIEW 8.5 and beyond
In LabVIEW 8.5, the
option to open LLB files in Windows Explorer has been removed. However,
if you have a previous version of LabVIEW installed along with 8.5,
LLBs can still be opened through Windows Explorer if you follow the
procedure below. If you are not using another version of Labview along
with 8.5, you can change the default behavior so that an LLB that is
opened from Windows will open the top-level VI instead of the LLB in
the LLB Manager.

Reading text files without specifying the encoding?

I have looked everywhere for a solution, but I can't find one. The problem is that I'm using codes that everybody is using, but for some reason, my codes aren't working.
I want to be able to open up text files in Java without having to specify the encoding for the files that I'm going read, because I have no idea which encoding they will use.
But even when specifying UTF-8 to be encoding of the file to read, it doesn't work correctly:
FileInputStream fileIS= new FileInputStream("somefile.txt");
Reader reader = new BufferedReader(new InputStreamReader(fileIS, Charset.forName("UTF-8")));
EVERYWHERE I look, ppl are using these codes! But it doesn't work, some characters (such as the Euro sign) are displayed as squares.
However, I want to be able to read not only UTF-8 files but anything that Java supports. Any ideas?
Edited by: Stalfos on Oct 22, 2007 12:22 PM

Stalfos wrote:
I want to be able to open up text files in Java without having to specify the encoding for the files that I'm going read, because I have no idea which encoding they will use.
This is your problem. If you don't know what encoding the text is stored in, then the chances that the default encoding used to read it will be correct are slim.
But even when specifying UTF-8 to be encoding of the file to read, it doesn't work correctly:There are many different character encodings, and most of them don't overlap. Anything above 127 usually causes problems.
FileInputStream fileIS= new FileInputStream("somefile.txt");
Reader reader = new BufferedReader(new InputStreamReader(fileIS, Charset.forName("UTF-8")));
EVERYWHERE I look, ppl are using these codes! But it doesn't work, some characters (such as the Euro sign) are displayed as squares.The problem isn't with the code, it's that the file you're reading isn't using an encoding that's compatible with UTF-8. Assuming that using UTF-8 should work for all encodings is like assuming that someone who can read Chinese should be able to read a book written in Spanish or Greek. It doesn't work that way.
However, I want to be able to read not only UTF-8 files but anything that Java supports. Any ideas?You need to know what encoding your files are stored in, period. There are a few ways to guess what the encoding is, but they're only reliable for a small set of encodings.
You don't seem to truly understand what character encodings are, or how to use them, so read this:
The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)
http://www.joelonsoftware.com/articles/Unicode.html

[svn] 1170: compiler: renaming the Compiler classes

Revision: 1170
Author: [email protected]
Date: 2008-04-09 16:17:57 -0700 (Wed, 09 Apr 2008)
Log Message:
compiler: renaming the Compiler classes
* flex2.compiler.abc:Compiler to AbcCompiler
* flex2.compiler.as3:Compiler to As3Compiler
* flex2.compiler.css:Compiler to CssCompiler
* flex2.compiler.i18n:Compiler to I18nCompiler
* flex2.compiler.mxml:Compiler to MxmlCompiler
Bugs: n/a
QA: Yes
Doc: No
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/Source.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/MetaDataParser.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/genext/GenerativeSecondPassEv aluator.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/AsDocAPI.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/ImplementationCompiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/ImplementationGenerator.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/InterfaceCompiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler_en.properties
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler_ja.properties
flex/sdk/trunk/modules/compiler/src/java/flex2/tools/WebTierAPI.java
Added Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/abc/AbcCompiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/As3Compiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/CssCompiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/i18n/I18nCompiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/MxmlCompiler.java
Removed Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/abc/Compiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/Compiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/Compiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/i18n/Compiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/Compiler.java

In the properties of your project, there is a page called "Java Build Path". On the bottom of that page, there is this field "Default output folder" in which you can specify to which directory Eclipse should write the .class files.
Then, for the build options, go to the Run Dialog (Run menu, Show Run Dialog). There you might have several configurations for several programs. Select yours, and go to the Arguments tab. There you have fields for program arguments (the String [] args), and VM arguments (like the -DProtoge.dir=)
Good luck!

Getconf returns compiler flags that the compiler warns about

I have Workshop 12u1 installed on my Solaris 10u8 machine (x86_64). I'm up to date with patches as of a couple weeks ago.
I'm well aware that the Workshop suite has deprecated flags like -xarch=generic64, -xarch=amd64a, etc.
However, when I run "getconf" on my Solaris 10 system, some of the conf settings still return those older flags that the compiler now warns about. That causes a lot of warning chatter when building certain applications (e.g. perl 5.10.1) that are smart enough to use "getconf" to try determine what flags to use in certain situations. Using getconf to find the right flags is even mentioned in the standards(5) page, but following its advice results in deprecation warnings from the compiler. Not good.
If you run the following code you'll see what I mean:
for f in `man getconf | egrep 'XBS'`; do echo "Checking $f"; getconf "$f"; doneIs this something that I (as a sysadmin for the system) should be able to configure, or is it something that would need to be patched to fix? The man pages for getconf, sysconf, and confstr aren't clear where the values are actually coming from.
So, how should this be fixed?
Thanks,
Tim

Enchanter wrote:
Since I'm running regular old Solaris 10, rather than OpenSolaris, I'm skeptical how much help the OpenSolaris developers are truly going to be. I can certainly give it a go, but even if they fix it in OpenSolaris, it might be a very long time before that fix filters into Solaris.Actually, it goes the other way. New features and modification go into the internal Solaris development workspace before they migrate to Open Solaris. The Solaris Express and final releases and Open Solaris releases come from the same source base. Whether a feature or update goes into a Solaris 10 patch depends partly on demand, especially demand from customers with service contracts.
I'm also a little puzzled about the "backwards compatibility" thinking of the compiler developers. In some areas (e.g. C++ and the standard library), what's shipped with the compiler is years and years behind what's current, apparently in the name of "backward compatibility". Yet where compiler flags are concerned, the developers seem to be much more cavalier about deprecating things and making changes that break backward compatibility.We try very hard not to break code or makefiles. Sun (and now Oracle) makes its money from enterprise users. Their code bases last for a long time, and changes are expensive. Changing a line in a makefile or source code file can mean having to re-certify the application.
The change from -xarch to -m specifying the memory model was more abrupt than we would have liked, and in hindsight, was probably not handled very well. We were running into combinatorial explosion of -xarch sub-options due to the increasing number of architectures that the compiler supports. Some option combinations quietly resulted in behavior that you didn't expect. (For example, the combination "*-fast -xarch=v9*"did not give the same result as "*-xarch=v9 -fast*".) Separating memory model from the other considerations made the options easier and more reliable to use.
Don't get me wrong -- I'm all for forward progress with the tool-chain -- I think that the C++ standard library and the defaults should all be brought up to what's current in the industry. Sun Studio 12 update 1 has direct support for Apache stdcxx (if installed in a standard location) in addition to libCstd and STLport. The Apache library will be in the next Open Solaris. When it will be available in a Solaris 10 update has not yet been decided.
I also think adding support for -m32/-m64 was a good move. It just seems to me that if the developers are going to deprecate a large number of flags that the compiler accepts, they should also make certain that the rest of the operating system can handle that change. To me, that means that they need to work with the developers of getconf/confstr() to make certain it knows how to check the compiler version before it emits a particular flag.Only a few options have been deprecated. It's just that they are probably the ones you used most. :-(
More than one compiler version can be installed on a system, and compilers can be installed anywhere. Programmers in medium to large shops typically run compilers installed on a remote server, although they might have other compilers installed locally. If getconf had to guess what compiler you were using, it would often guess wrong. If you have suggestions on how to match up getconf behavior with the compiler you want to use, please post them in an Open Solaris forum.

Is it allowed for unused variables to be optimized away by the compiler?

Let's assume I have the following code:
public void myMethod() {
   final Object x = new Object();
   // I never refer to x.
   // other code, for example:
   System.out.println("lala");
}The question I have is: what is the earliest possible moment that x can be garbage collected?
I have checked the JLS and JVM spec, but I cannot find the answer. It seems to me, that the assignment to x causes a local variable slot in the stack frame to be assigned a reference to x, and therefore, x cannot be garbage collected until after the method returns since there is a strong reference to x during the entire method call. But maybe the compiler might be allowed to compile away the unused local variable, resulting simply in the code: new Object(), which would then create an object which immediately has no strong references, and can be collected before the println. Does anybody know the correct answer?
Regards,
Sebastiaan

sebster wrote:
On what do you base this assertion? Do you have any references?The problem is that I can't remember if I read it in a document related to garbage collection or if it was in the VM specification (the language specification does not specify that a GC must exist if I remember it correctly).
One thing that shows what I told you currently is true is that this code:
public class ByteCode {
    public void myMethod() {
        final Object x = new Object();
        System.out.println("lala");
}Compiles into this using the Sun compiler for Java 6.
public ByteCode();
Code:
   Stack=1, Locals=1, Args_size=1
   0:   aload_0
   1:   invokespecial   #1; //Method java/lang/Object."<init>":()V
   4:   return
LineNumberTable:
   line 21: 0
public void myMethod();
Code:
   Stack=2, Locals=2, Args_size=1
   0:   new     #2; //class java/lang/Object
   3:   dup
   4:   invokespecial   #1; //Method java/lang/Object."<init>":()V
   7:   astore_1
   8:   getstatic       #3; //Field java/lang/System.out:Ljava/io/PrintStream;
   11: ldc     #4; //String lala
   13: invokevirtual   #5; //Method java/io/PrintStream.println:(Ljava/lang/String;)V
   16: return
LineNumberTable:
   line 23: 0
   line 25: 8
   line 27: 16
}Note the call to astore_1 that is the assignment to the local variable.
Kaj
Ps. looks like the forum has a bug in the handling of the pre tag. :(
Edited by: kajbj on Feb 14, 2008 5:09 PM

The mxmlc compiler displays the compilation errors in Japanese - and I want them in English!

Working in a Japanese company I have to use a machine with
Windows XP in Japanese. The thing is that I can barely read this
language so it's really depressing when most Java apps (and Flex,
through Eclipse, is one of them) outsmart themselves and default to
displaying their UI strings/messages in Japanese
without giving the user the ability to select another
language.
When compiling Flex apps using Flex Builder 2, the mxmlc
compiler is internally called by the IDE to perform the compilation
and then its output is displayed in the Problems View.
Well, the English version of mxmlc, has all its messages
(compilation warnings, errors etc) translated into Japanese (as far
as I can tell, they are hardwired into the exe). So although I'm
using the English version of the FB2,
with -locale en_US specified as an argument for the
compiler, all the compilation erros are reported in Japanese!
Even after changes in "flex-config.xml" and "jvm.config" as
you can see below, the compilation errors are still in Japanese. I
started to doubt that there's a solution to this problem but I
really hope there is one.
TIA,
.x.
Here are the relevant portions of my config files and an
example of mxmlc's output (Japanese might not display correctly):
-- C:\Program Files\Adobe\Flex Builder 2\Flex SDK
2\frameworks\flex-config.xml --
<flex-config>
<compiler>

<accessible>false</accessible>

<locale>en_US</locale>
</compiler>
</flex-config>
-- C:\Program Files\Adobe\Flex Builder 2\Flex SDK
2\bin\jvm.config --
# Arguments to VM
java.args=-Xmx384m -Dsun.io.useCanonCaches=false
-Duser.language=en
-- mxmlc invoked on the command line --
mxmlc -o ASCIIArt -locale en_US ASCIIArt.mxml
Loading configuration file C:\Program Files\Adobe\Flex
Builder 2\Flex SDK 2\frameworks\flex-config.xml
ASCIIArt\AsciiArtBuilder.as(7): col: 45 Error:
定義
com.example.programmingas3.asciiArt:BitmapToAsciiConverter
が見つかりません。
import
com.example.programmingas3.asciiArt.BitmapToAsciiConverter;
^
ASCIIArt\AsciiArtBuilder.as(8): col: 45 Error:
定義 com.example.programmingas3.asciiArt:Image
が見つかりません。
import com.example.programmingas3.asciiArt.Image;

inlineblue you are right about the "-locale" switch. I've
just found this page on live docs:
http://livedocs.macromedia.com/flex/2/docs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=L iveDocs_Parts&file=00001500.html
with all the compiler options
I thought that "-metadata.language <code>" (alias
"-language") sets the language, but it seems that it's only for
metadata.
So -locale is out. Thanks for clearing this for me. There's
one more path left...
As I wrote in my first message, besides the "-locale en_US"
compiler option, I am also setting the "user.language" flag in
jvm.config to "en":
-- C:\Program Files\Adobe\Flex Builder 2\Flex SDK
2\bin\jvm.config --
# Arguments to VM
java.args=-Xmx384m -Dsun.io.useCanonCaches=false
-Duser.language=en
According to the docs:
http://livedocs.macromedia.com/flex/2/docs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=L iveDocs_Parts&file=00001462.html
this is the standard (only?) way to pass arguments to the JVM. And
AFAIK "-Duser.language=en" is supposed to set the user language to
English. But it does not happen... I have to investigate this
more...

Any way to run the processor before the compiler throws an error?

Hi,
I want to generate code for an annotation @OverrideAll that would implement all the interface I methods with some default body.:
Example
interface I {
void method();
@OverrideAll
class A implements I {
}would have to generate code like this:
class A_gen implements I {
public void method() {
class A extends A_gen {}However, I have the problem that the original source file does NOT compile because the interface I is not implemented, and as such, the annotation processor never runs. My question is:
Is there any way I could force the annotation processor to run before the compiler shows the error? Or at least some way to supress this error message and give a chance to the annotation processor to run?
TIA,
Gabriel

belingueres wrote:
Hi,
Thanks for answering so soon.
I would prefer not to name the generated class in the original source code. As an alternative I thought to rather generate a subclass, but then there is the instantiation problem (can´t do it without creating a factory method in class A and making it abstract, and indeed again need to name the generated class):
@OverrideAll
abstract class A implements I {
public static A create() {
return new A_gen();
// generated class
class A_gen extends A {
public void method() {
}so it seems I reached a dead end here.
It would really help if (using the superclass generation as originally posted) I could change in the processor the superclass of class A to be A_gen, but it would require AST rewritting and I guess it is not a good option (if at all possible.)Belingueres,There are two ways to do what you want. You can either generate a superclass of A, or a subclass of A.
If you generate a superclass, you need to specify the generated superclass's name in the extends clause of A. But you said "I would prefer not to name the generated class in the original source code", but give no reasons then go off exploring the second alternative.
If you generate a subclass of A, then you need a way for the rest of the code to instantiate As without really knowing about the subclass, so you do in fact need a factory method in A which actually returns A_gens.
I suggest you revisit your preference for not naming the generated class, and work out why you have that preference, and whether it is actually a sound engineering constraint, an aesthetic nicety (maybe in terms of not wanting the implemention strategy to be brought to the surface) or something emotional.
You can do what you want with annotation processing, but you must choose between naming the generated superclass in the extends, or having an factory method that names the subclass.
A related issue is that if you generate the superclass, the annotation processor can pick up the name of the class to be generated from the "extends" clause, and you therefore don't need to specify it any other way, whereas if you generate a subclass, the annotation processor cannot infer the name of the subclass that is being instantiated from the factory method (unless you use non standard APIs in your annotation processor), which means you need to explicitly name it as an attribute of the annotation.
I have a preference for generating a superclass because that imposes less restrictions on whatever else you do with the class, and less of the code generation implementation details leak up into the class's signature.
Also note when generating a superclass, if you want to extend something other than Object, then you need to specify that as an annotation value, usually as a Class<?>.
Bruce

Specifying the character set for Web Services

Hi
When i set the weblogic system property
-Dweblogic.webservice.i18n.charset=utf-8
I get an error from weblogic douring startup
<BEA-141087> <Unrecognized property: webservice.i18n.charset.>
I'm using wls 8.1.
Shouldn't this be the way to specify the encoding for web services
Regards
Preben

Is it a Warning or a Error?
If it is WARNING it is a known issue with the logging.
The charset you set should work fine.
Ajay
"Preben" <[email protected]> wrote in message news:[email protected]..
>
Hi
When i set the weblogic system property
-Dweblogic.webservice.i18n.charset=utf-8
I get an error from weblogic douring startup
<BEA-141087> <Unrecognized property: webservice.i18n.charset.>
I'm using wls 8.1.
Shouldn't this be the way to specify the encoding for web services
Regards
Preben

Changing the compiler in the SDK when building a BSP for a Zynq

Hi,
I have a zedboard and I need to get software running in a bare bones AMP situation using the IAR compiler. There is an eclipse plugin that I've manged to add to the SDK and I can get non BSP apps to use the IAR compiler, but not build/link as the BSP wont build with IAR.
Looking through the SDK files I can see that there are some files to support the IAR compiler (C:\Xilinx\SDK\2015.2\data\embeddedsw\lib\bsp\standalone_v5_1\src\cortexa9\iccarm) however I can't figure out how to point the BSP at these files instead of the GCC ones.
I feel like there's something simple I'm missing, like there should be an option in the BSP generation process or something.
Has anyone else tried to go this?
This was from a custom hardware design exported from Vivado 2015.2.
Thanks

Thanks, these helped a lot.
I had to add the complier directory to my PATH variable.
I found that I couldn't use the GUI to change the compiler flags and it kept passing -O2 -c to the compiler, neither of which are valid for IAR. So I had to manually edit the make file, this causes a problem if I try and re-open the options via the GUI and re-generating the sources deletes my change, but it does work.
A couple of the other make files needed modifiying as well, XCoresightPs - needed to specify the cpu (IAR option --cpu= Cortex-A9) and the XGpio make file just needed a complete re-write no idea what was going on there, I copied a working one and changed the names.
Also, for any other IAR users out there; --diag_suppress=Pa050 is a must, (removes warning about non native line endings)

How can I get to the compiler arguments in Flash Builder 4.6?

Howdy!
So far I've been unable to locate any information that could help me with my task. The ultimate goal is to build my project's SWF with mxmlc. I was not able to figure it out and thought I'd install Flash Builder in the hopes of being able to get to the compiler arguments. No luck.
First, I'm not the lead on the building of the SWF. This is done by another person via the Eclipse plugin; her hard drive crashed last night too. In fact I'm not a Flash developer. I'm coming at this from a Build Infrastructure perspective.
Any help would be greatly appreciated.
Cheers,
Mel Riffe

Mel Riffe,
Here's a Help topic about compiler options in Flash Builder: http://help.adobe.com/en_US/flashbuilder/using/WSe4e4b720da9dedb524b8220812e5611f28f-7fe7. html
For information on using mxmlc, the application compiler, to compile SWF files from your ActionScript and MXML source files, you can see: http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7fcc.html
Hope this helps,
Mallika Yelandur
Flash Builder Community Help & Learning
Adobe Systems Incorporated

How do I specify the gmail outgoing server if I have multiple gmail accounts in my mail? I have 2 business accounts and when I send mail from one account, it is sent from the other account and the sending email is not from the correct account.

I love my apple email and do not want to use google mail on safari. However, I have 2 gmail accounts set up on apple mail, but when I send mail from one of my gmail accounts (I choose the specific gmail account in the drop down window), it actually goes out as if it is from the other gmail account. I can't have that happen because one is my job, the other is a personal business account and unfortunately, the mail from both gmail accounts want to send through the personal business account. How do I make it send from a specific gmail account? I even tried deleting the accounts and setting them up again hoping I set it up wrong in the first place, but to no avail, it is still doing the same thing except this time I set the job account up first and then the personal business account and now everything goes from the job account! The only good thing is that the incoming messages work properly and they go into the correct inbox. Somebody please fix my outbox!

In Mail Preferences/Accounts/each GMail account, set up the SMTP Outgoing Server for each account separately, going into SMTP name/edit/Advanced and specify the Username of each account. The Outgoing servers must be two different servers, authenticated by the Username and Password of each.
Otherwise, the GMail SMTP server will change the from address to that of the account where the SMTP server was setup.
Ernie

Specifying the charset to the compiler

Similar Messages

Maybe you are looking for