Showing messages 1 through 21 of 21.

• 上海写字楼
  2008-10-05 19:21:51 sknuckles [Reply | View]
  
  传统的上海商业地产在当前正面临痛苦的决断，在部分城市，随着北京写字楼市场的量价齐跌，“断供”、“抛售”等现象正日益刺激着投资者已经脆弱的信心，回报率下降、投资风险增加，使得上海办公楼类产品的投资价值正遭受着空前的置疑，那么在目前股市走熊、住宅低潮的情况，是不是所有的房产产品都不具备投资价值呢？其实不然，上海写字楼、商铺、上海商务楼等商务性质的房产产品依然保有较高的投资价值，目前在广州、上海等发达城市，上海写字楼租赁与功能多样化的办公楼出租正成为投资者的新宠。
  一元租金写字楼
  二元租金写字楼
  三元租金写字楼
  四元租金写字楼
  五元租金写字楼
  六元租金写字楼
  七元租金写字楼
  八元租金写字楼
  九元租金写字楼
  十元租金写字楼
  十五元租金写字楼
  二十元租金写字楼
  商铺
  商住楼
  商务中心
  创意园区
  厂房
  酒店公寓
  随着物权法的完善，“住宅禁商”的逐步实施，这些企业将不得不寻求于上海写字楼或
  上海办公楼。中小型企业多为成长型，企业发展战略多存在不稳定性，低成本入驻与较高的外在形象是这类企业考虑办公场所的重点，而上海办公楼的租售价格、物业管理费用相对较高，更多的中小型企业会选择既能满足上海写字楼出租的用途，又可以实现居住功能的商住楼商务楼。客源上的充足保证了商用办公房的低空置率，写字楼租金回报更稳定。
  更多链接；
  上海办公楼中介
  上海浦东办公楼
  静安区办公楼
  黄浦区办公楼
  长宁区办公楼
  卢湾区办公楼
  徐汇区办公楼
  普陀区办公楼
  上海商铺出租
  上海厂房租赁
  上海创意产业园区租赁
  上海商务中心出租
  华敏翰尊
  虹桥银城
  上海华都大厦
  胜康廖氏
  华源世界广场
  沙田大厦
  彩虹QQ
  BIKE
  金融危机，金融风暴
  麻风树
  蝇蛆
  汽车
  qq游戏马 QQ记牌器下载
  qq空间全黑背景代码
  qq空间蓝色背景代码
  qq空间白色背景代码
  qq空间粉色背景代码
  qq空间小窝背景代码
  梦幻西游qq表情下载
  炮炮兵qq表情下载
  黄金价格
  黄金价格走势，黄金价格（每盎司）
  今日黄金价格，黄金价格（每克）
  国际黄金价格，黄金价格（每公斤）
  汇率换算，各国汇率换算
  上海办公楼中介
  浦东办公楼中介
  静安写字楼，静安办公楼中介
  黄埔写字楼，黄埔办公楼中介
  徐汇写字楼，徐汇办公楼中介
  卢湾写字楼，卢湾办公楼中介
  上海办公楼中介
  浦东办公楼出租
  静安写字楼租赁
  上海黄埔办公楼
  长宁区写字楼租赁
  卢湾写字楼租赁
  徐汇办公楼出租
  普陀写字楼租售
  创意园区
  商务中心
  上海写字楼中介
  浦东办公楼
  静安办公楼
  黄埔办公楼
  徐汇办公楼
  卢湾办公楼
  上海写字楼中介
  上海写字楼中介
  上海办公楼，上海办公楼中介
  黄浦区办公楼，上海黄浦区办公楼租售
  徐汇区办公楼，徐汇区办公楼租赁
  静安区办公楼，静安区办公楼出租
  浦东办公楼，上海浦东办公楼
  长宁区办公楼，长宁区办公楼中介
  上海办公楼，上海卢湾区办公楼

• You might want to invoke some method
  2007-03-01 08:00:36 pinpinokio [Reply | View]
  
  You might want to invoke some method in the condition and check the result of this invokation. If the result doesn't satisfy you, you can do nothing. Probably something like :
  if (!(iterator = iter.next())) ;
  else ...

• well i am also wondering why?
  2006-11-02 11:23:07 prasanth_jvrs [Reply | View]
  
  

  Well guys,even compiler is not complaining when we put semicolon anywhere after curly braces except like do while etc... for example it didnot complain when we put; class IfTrueExample {;;;; public static void main(String[] args) {;;; static void m1() {;;; ......... so on

• well i am also wondering why?
  2008-10-02 13:41:16 oyunara [Reply | View]
  
  oyunlar sohbet odaları oyunlar video oyun
  
  
  thank you for comment
• well i am also wondering why?
  2006-11-02 11:37:54 prasanth_jvrs [Reply | View]
  
  It is looking like semicolon is processed as part of compiler instructions so it depends on the statement when compiler will complain.
  
  Like class IfTrueExample {;;;; here all semicolons will be processed and it will ignore as the empty semicolons will be ignored...but the case of return;;; it will complain from the 2nd semicolon as it cannot process the instructions after 1st semicolon.So it really depends on the instruction given to compiler

• why not raise a bug?
  2006-10-28 02:05:16 asjf [Reply | View]
  
  to me, this is clearly the kind of check the compiler should make as the odds are that 100% of the time this appears in code, someone has made a typo that will likely lead to a bug. If you feel strongly, then why not raise a bug against the language spec? it might break some existing code, but it should break that code imho

  Empty statements in the for loop are common and differ as they can be used legitimately

  Tools that generate code can easily introduce a dummy method doNothing() or dummy statement to work around this

• why not raise a bug?
  2007-03-16 11:55:18 dividezero [Reply | View]
  
  I would instead suggest that instead of raising a compiler error, make it a warning, the same the compiler creates warnings for:
  
  int foo = 6;
  foo = foo;
  
  the ;;;;;;;;'s in question are probably being caught as "lines of code" but since they do nothing, they are eaten by the compiler and make no change in the bytecode.

• Use Lint4j or other static analysis tools
  2006-10-25 21:36:03 sreich [Reply | View]
  
  I added an audit for exactly this case to Lint4j, which audits Java source code for obvious and not so obvious coding problems.
  When you use the Eclipse plugin with the builder support, the warning will pop up the moment the file is saved.

• Compiler is meant for only Syntax Checking
  2006-10-25 11:22:54 sunnyjava [Reply | View]
  
  Resposibility of compiler is just to compile the code from one form to another without looking into the correctness,performance etc issues.
  But it would be helpfull to have command line options(possibly in -X list) to scan such things.
  the same question applies for string comparision(== or equals),overiding equals() without overiding hashcode(),etc.
  Again code review tools are there to catch such mishaps, so still we can keep compiler out of this issues.

• Because empty statement are allowed
  2006-10-24 11:19:07 farnulfo [Reply | View]
  
  Empty statement are allowed in java grammar like :
  java code :
  ;;
  
  I remembered that in ADA language empty statement are not allowed, if you don't want to do anything you must say it by using null keyword:
  ADA code :
  ;; => compiler error
  you must use : ; null ;
  
  ADA is one of the most compiler checking language I have seen : when you use a switch statement with a integer and you only have case 1, .. case 3 , you've got a compiling error that interval [-999999999,0] and [4,9999999] are not defined !
  ANd this is an error not a simple warning : You must use a default statement.
• So, why are they allowed in Java then?
  2006-10-24 12:02:42 nielsull [Reply | View]
  
  As several people have pointed out, the compiler allows it because the Java standard allows it. And, yes, there are several tools that will catch errors like these.
  So, the real question is: Why does Java allow this?
  
  It doesn't make much sense, if you think of Java purely as a language humans write code in.
  
  But Java is also used as an intermediate language, e.g. for JSP pages. And sometimes JSP is generated automatically (e.g. using XSLT). When developing systems like this, it does make life a lot simpler if you are allowed an occasional empty statement,
  so that you can write stuff like
  
  <myframework:if cond="useTop">;<%@ include file="userWrittenTop.jsp" %>;<%/myframeworktaglib:if>
  
  Now, if the framework user happens to want to use a blank userWrittenTop.jsp? Should he get a Java compiler error, which he cannot really do anything about?
  
  PS: Don't point fingers at this (ab)use of JSP - my point is that Java should not disallow it.
  And in real life, the code may be a lot more complex.

• FindBugs
  2006-10-24 10:06:34 smbell [Reply | View]
  
  As others have said this is not the place of the compiler. This is more the place of static analysis tools like FindBugs.
• FindBugs
  2006-10-24 14:48:34 jadonohu [Reply | View]
  
  Well, the compile will fail in other scenarios where the code is syntactically correct but obviously wrong ... e.g., if you are catching an Exception that is never thrown, or other cases of unreachable code. I assume this might have been the original posters point.
  
  I'm guessing the reason for allowing a no-op statement following an "if" is to allow something like:
  
  if (some-test)
  {
  // do nothing ... pretty much the same as a ";"
  }
  else
  {
  code here ...
  }
  
  To the compiler, I assume the empty brackets are effectively the same as a semi-colon. I write conditionals like this if it makes the code more clear.
• FindBugs
  2007-07-16 21:23:29 3ufblogg [Reply | View]
  
  Stupid Questions 16: What's the Difference Between Wildcard Generics and no Generics?

• Chalk this up to coding conventions
  2006-10-24 07:55:49 jgustie [Reply | View]
  
  I think this is definitely a case where following Java's coding conventions to write readable code helps. Section 7.4 of Sun's coding conventions for Java suggest that you use:

  if (condition) {
      statements;
  }
  

  This helps prevent the problem above, though I imagine it sparks a heated debate about where the curly bracket belongs.

  When using an IDE, running the code formatter can help spot this type of bug as well. When formatted with Eclipse using the Java conventions, the example above becomes:

  if (condition)
      ;
  {
      statements;
  }
  

  It is much clearer using properly formatted code that there is a problem.

• Not the compiler's job
  2006-10-24 07:08:44 jattardi [Reply | View]
  
  The compiler's job is to simply parse Java code and make sure all the statements are valid. A single semicolon is a valid statement, and all an if statement needs is one valid statement following it.
  
  Checks like these are better left to a source code analysis tool, something like FindBugs or Checkstyle.

• use for an empty statement
  2006-10-24 06:56:33 schack [Reply | View]
  
  It might be useful (although I cannot imagine a concrete example) that you only want to use the side effects of the condition.
  Like:
  If ( Sammy.loves(Rosie) || Rosie.hates(me));
  with both functions doing stuff before returning a boolean and Rosie.hates(me) only being executed in case Sammy.loves.(Rosie) has returned false.

• Empty statements are allowed
  2006-10-24 05:07:28 mnesarco [Reply | View]
  
  Its just like a for statement with an empty block:
  for (i=0; i<100; i++);
  I think the semantics of the program is not a compiler problem.
• Empty statements are allowed
  2006-10-24 09:43:17 afishionado [Reply | View]
  
  

  On that thread,

  
  for (;;)
      foo();
  

  is valid syntax as well, only the no-ops are in the conditional, not the body.

  Basically, anywhere you can put a statement, you can put an empty statement, and the compiler doesn't care.

• Empty statements are allowed
  2006-10-24 23:29:43 rbirenheide [Reply | View]
  
  

  That is not entirely the case:

  
  return;;
  
  

  will not compile. In that case the compiler does take the decision whether your empty statement makes sense or not.

• Empty statements are allowed
  2006-10-25 04:55:26 jwenting [Reply | View]
  
  But for an entirely different reason, as your empty statement is unreachable code. Anything else there would also be rejected!

  An empty statement may be intentional, therefore the compiler will allow for it. Possibly an explicit nop instruction like Assembly or Ada has would have prevented some errors, but the cost is code readability.