3 ms·
again a syntax error, you can't have generics in an expression in which operators such as > are allowed, the java syntax is really simple and unambiguous to par
by riffraff 16y ago
again a syntax error, you can't have generics in an expression in which operators such as > are allowed, the java syntax is really simple and unambiguous to parse.
On the other hand, [] is used for arrays in java so it _would_ conflict with something
- beagle3 16y agoSee this comment above in this thread: http://news.ycombinator.com/item?id=2442468 http://news.ycombinator.com/item?id=2442468 It is a semantic error, not a syntax error (in the sense that an annotated grammar CANNOT, without semantic analysis, find that this is an error). The example given in this comment, F(G<A,B>(7)) is syntactically ambiguous and can only be resolved to either F( (G<A) , (B>(7) ) - a two argument function call, or F( (G<A,B>(7)) ) - a one argument function call - when the types of F, G, A and B are known. Also, things like F<G<A>> (which are perfectly legal) make lexing very hard - you can't assume '>>' is the shift right token without syntactic (and semantic) analysis. Or, you can decide like early C++ that you must write it F<G<A> > which is confusing.
- riffraff 16y agosorry, but are you sure a C# problem applies to Java? AFAIK the syntax for passing type arguments to a generic method in the latter would be obj.<A,B>G(7) so F(G<A,B>(7)) is once again unambiguous, at a syntactic level. It would seem the java designers thought of the issue :)