public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "mark at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/16843] New: gcjh generated headers don't define final constants Date: Sat, 31 Jul 2004 10:19:00 -0000 [thread overview] Message-ID: <20040731101911.16843.mark@gcc.gnu.org> (raw) Some JNI header generators like kaffeh output C #defines for final static (primitive and String) fields. gcjh doesn't do this. The output of running kaffeh on the following class: public class T extends Thread { public static final String Hello = "World"; public static final float f = 1.4f; public static final double d = Math.PI; } gets you the following defines in T.h: #define T_MIN_PRIORITY 1 #define T_NORM_PRIORITY 5 #define T_MAX_PRIORITY 10 #define T_Hello "World" #define T_f 1.4000000e+00 #define T_d 8.6191995128153828e+97 Note that some of these constants come from the super class. Also note that the float and double results look like bugs in kaffeh. Unfortunately I cannot find the specification that defines this behaviour. -- Summary: gcjh generated headers don't define final constants Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mark at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org,robilad at kaffe dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16843
next reply other threads:[~2004-07-31 10:19 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-31 10:19 mark at gcc dot gnu dot org [this message] 2004-08-05 6:42 ` [Bug java/16843] " pinskia at gcc dot gnu dot org 2004-11-08 6:30 ` tromey at gcc dot gnu dot org 2004-11-08 18:03 ` cvs-commit at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040731101911.16843.mark@gcc.gnu.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).