| 1 |
wu chuanwen wrote: |
| 2 |
> 2006/5/13, Boyd Stephen Smith Jr. <bss03@××××××××××.net>: |
| 3 |
> |
| 4 |
>> Change your system javac to a 1.4 for the emerge of commons-daemon. The |
| 5 |
>> resulting class/jar files will run in a 1.5 vm -- since enum and assert |
| 6 |
>> (introduced in 1.4) are both still valid identifiers in bytecode under a |
| 7 |
>> 1.5 vm. |
| 8 |
> How can i change my javac to 1.4?You mean re-emerge sun-jdk1.4? |
| 9 |
|
| 10 |
That's probably what he mans. |
| 11 |
|
| 12 |
> Is |
| 13 |
> there any other ways? |
| 14 |
|
| 15 |
Why? That's a good enough way, IMO. |
| 16 |
|
| 17 |
> Thanks! |
| 18 |
>> |
| 19 |
>> Bytecode also allows two methods with the same name that only differ in |
| 20 |
>> return type, which allows generics that only compile under 1.5 (and |
| 21 |
>> modified versions of 1.4) javac to work under a vm as far back as (at |
| 22 |
>> least) 1.2 -- as long as the requisite libraries are in place. |
| 23 |
>> |
| 24 |
>> Sun and the JCP have been very good to modify the bytecode specification |
| 25 |
>> sparingly, if at all, so that valid class files output from any javac will |
| 26 |
>> run on almost all vms. This common binary format goes a long way toward |
| 27 |
>> the goal of WORA. |
| 28 |
>> |
| 29 |
>> -- |
| 30 |
>> "If there's one thing we've established over the years, |
| 31 |
>> it's that the vast majority of our users don't have the slightest |
| 32 |
>> clue what's best for them in terms of package stability." |
| 33 |
>> -- Gentoo Developer Ciaran McCreesh |
| 34 |
|
| 35 |
PS: Please delete text which you don't need, like the one which |
| 36 |
I've just quoted. |
| 37 |
|
| 38 |
Alexander Skwar |
| 39 |
-- |
| 40 |
Would ye both eat your cake and have your cake? |
| 41 |
-- John Heywood |
| 42 |
-- |
| 43 |
gentoo-user@g.o mailing list |
Archives