Java 中，+ 号连接的多行文本，与单行文本的有区别吗？

在代码编写中，经常会有一长串的文本，为了阅读方便，一般是以多行输入的。在 C# 中，可以使用 @ 符来指定这是一个多行文本块，但是在 Java 中，并没有找到类似的语言特性，所以我只能用 + 号来连接多行文本，并以为这与单行文本，最终的处理方式是不一样的，会浪费 CPU 资源，进行字符串拼接。


如下面的代码：

   public ArrayList getPage(EnterpriseForm formBean, Integer pageNo) throws Exception{
       ArrayList result = new ArrayList();
       // SQL文
       SQLBuilder sql = new SQLBuilder("SELECT id, code, category, name, phone1, fax1, phone2, fax2, " +
               "email, url, address, keyword, " +
               "bank_name1, bank_account1, bank_account_name1, " +
               "bank_name2, bank_account2, bank_account_name2, " +
               "bank_name3, bank_account3, bank_account_name3, " +
               "contact1_name, contact1_phone1, contact1_phone2, contact1_phs, " +
               "contact1_mobile1, contact1_mobile2, contact1_email, " +
               "contact1_qq, contact1_msn, contact1_skype, " +
               "contact2_name, contact2_phone1, contact2_phone2, contact2_phs, " +
               "contact2_mobile1, contact2_mobile2, contact2_email, " +
               "contact2_qq, contact2_msn, contact2_skype, " +
               "contact3_name, contact3_phone1, contact3_phone2, contact3_phs, " +
               "contact3_mobile1, contact3_mobile2, contact3_email, " +
               "contact3_qq, contact3_msn, contact3_skype, " +
               "memo, " +
               "regist_user_id, regist_time, update_user_id, update_time " +
               "FROM enterprise");

但是一想，编译器难道不会作优化处理么？
为了验证，使用 jadnt158 进行了反编译，验证了这个想法。
结果不出所料，从而可以没有顾虑地使用多行字符串了。


上面代码反编译后的结果：

   public ArrayList getPage(EnterpriseForm formBean, Integer pageNo)
       throws Exception
   {
       ArrayList result = new ArrayList();
       SQLBuilder sql = new SQLBuilder("SELECT id, code, category, name, phone1, fax1, phone2, fax2, email, url, address, keyword, bank_name1, bank_account1, bank_account_name1, bank_name2, bank_account2, bank_account_name2, bank_name3, bank_account3, bank_account_name3, contact1_name, contact1_phone1, contact1_phone2, contact1_phs, contact1_mobile1, contact1_mobile2, contact1_email, contact1_qq, contact1_msn, contact1_skype, contact2_name, contact2_phone1, contact2_phone2, contact2_phs, contact2_mobile1, contact2_mobile2, contact2_email, contact2_qq, contact2_msn, contact2_skype, contact3_name, contact3_phone1, contact3_phone2, contact3_phs, contact3_mobile1, contact3_mobile2, contact3_email, contact3_qq, contact3_msn, contact3_skype, memo, regist_user_id, regist_time, update_user_id, update_time FROM enterprise");