why it's NOT safe to replace a StringBuffer object with a StringBuilder in java version earlier than 1.5 -


good evening, read these statement in blog it's not safe replace stringbuffer object stringbuilder in java version earlier 1.5 , seems fact, there's no apparent reason !!, know stringbuffer extending class java.lang.abstractstringbuilder. stringbuilder extends abstractstringbuilder, inherits methods well.so compiler's point of view can safely replace stringbuffer stringbuilder. of course stringbuilder not synchronized, if care synchronization can't replace string buffer string builder in point of view synchronization factor think of when replacing string buffer string builder, seems there's factor java version don't know how these effects decision, please discuss these point me.

the reason it's not safe use in vm before 1.5 because stringbuilder didn't exist before 1.5. if @ javadoc stringbuilder can see has exited since 1.5.

regarding when use in 1.5+, safe in substituting stringbuffer out in favor of stringbuilder. case when wouldn't want if have more 1 thread writing buffer. however, in cases when want make string , return it, tostring() method, instance, should safe.


Comments

Popular posts from this blog

ios - iPhone/iPad different view orientations in different views , and apple approval process -

java Extracting Zip file -

C# WinForm - loading screen -