Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><em>&lt;copied from comment&gt;</em> Dalvik does not conform to any JLS edition, because conformance requires passing <a href="http://en.wikipedia.org/wiki/Technology_Compatibility_Kit#TCK_for_the_Java_platform" rel="nofollow">JCK</a> which is not an option for Dalvik. <em>&lt;/copied from comment&gt;</em></p> <blockquote> <p>programmers really should know on which features of JLS they may rely when execute their code on Dalvik</p> </blockquote> <p>I think the only way for them to know is to study Dalvik test suite (I bet there's one and I expect it is open source isn't it?). For any feature you need, 1) try to find a test that would fail if <em>your feature</em> is implemented incorrectly and check if the test looks good enough. If there's no such test or it's not good enough, 1a) add new or improve existing test. Then, 2) find out if the test has been successfully run against your target implementation. If test hasn't run then 2a) run it yourself and find out if it passes or fails.</p> <p>BTW above is roughly about how <em>JCK</em> works. The main difference is that one has to invest own time and effort with Dalvik for things one gets from Sun/Oracle for granted. Another difference seems to be that for Dalvik this is not documented while <em>Snorcle</em> has clear docs on that iirc</p> <blockquote> <p>But there is no any words about this in documentation.</p> </blockquote> <p>well if there are no words on that then I'd say quality of Dalvik documentation is suboptimal. Softly speaking</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CO_Dalvik documentation is suboptimal_. There is no public Dalvik's documentation at all and API docs is not good too: e.g. you may find a description of constructor with return value (nice ;)) but it is very rare to see a useful notes on pre- and post- conditions for the methods. As to tests you are proposed ... well, someone may try but note following: what if you want to use any existing Java code library? it also seems that different versions of Android has the different versions of Dalvik, and what you will do if they has no reasonable common set of supported _features_?
      singulars
    2. CO@Alexey well the popularity of Android platform makes me feel that concerns you raise are not really that important. By the way for all the _what-if_'s you mention I for one can think of at least one way to address these - and none is rocket science, one can figure it by a little thinking and applying common sense. Quoting self, _one has to invest own time and effort with Dalvik_
      singulars
    3. CO_concerns you are raise are not really that important_. For users of Android's smartphones and tablets maybe. But I am personally not very happy with my Galaxy S and A500 due to the all these problems with browser (A500, hang ups), Android market (A500, is the application installation will success is 50/50), background worked Live Wallpapers (Galaxy S, just waste battery) and so on. Matter of quality. What I really want to know is asked in a initial post. Until I get answers I can't states that my code is quality (assumptions vs conformance), and as developer I am not happy with this.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload