Why EM is different from other VM component in regards to localization? If someone is interested in getting verbose VM output localized, it would not be good mixing lingos for them. Anyway, as Gregory pointed out, general problem remains - then we should drop localization in all plugguble components (GC, JIT etc). I suggest we think of fixing localization/logging instead.
-- Alexey 2007/6/4, Oliver Deakin <[EMAIL PROTECTED]>:
Sounds like this is the right solution to me. +1. Regards, Oliver Mikhail Fursov wrote: > On 6/4/07, Gregory Shimansky <[EMAIL PROTECTED]> wrote: >> >> I was hoping that it is possible to find a solution for this problem >> without loosing localization. Also looking at the stack that Oliver has, >> he has failures for LECHO in a place different from the stack in >> HARMONY-3772. So if we change LECHO to ECHO in EM it should be done in >> all places. >> >> I see no reasons to make EM output localized. Only JVM/launcher >> developers > will ever see it but not JDK-users. > If nobody minds I propose fixing this issue by replacing all LECHO to > ECHO > as Gregory said. > -- Oliver Deakin Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
