4 ms·
Well, take a look at this sample (http://dispatch.databinder.net/Common_Tasks http://dispatch.databinder.net/Common_Tasks) and see if you can figure out what al
by tomh- 16y ago
Well, take a look at this sample (http://dispatch.databinder.net/Common_Tasks http://dispatch.databinder.net/Common_Tasks) and see if you can figure out what all those operators do just by looking at them :)
Thats the kind of abuse possible with languages such as Scala, Haskell or c++ templates.
- fogus 16y agoTake a look at this sample (http://static.springsource.org/spring/docs/2.5.x/api/org/springframework/aop/package-summary.html http://static.springsource.org/spring/docs/2.5.x/api/org/spr...) and see if you can figure out how to use these classes just by looking at them. That's the kind of abuse possible with languages such as Java. --- Seriously. Every new API that you intend to use has a learning curve, some more significant than others. Every new API is a new "language".
- Stormbringer 16y agoIt's not really a fair objection. AOP isn't part of Java, it is an ugly hack that someone bolted onto the outsides of it. Seriously. You write your Java code, you compile it, and then in the night the evil AOP pixies sneak in and slip chunks of bytecode into your compiled classes.
- scott_s 16y agoThe library tomh linked to is not a part of the Scala language or the standard library.
- nl 16y agoI think if you are familiar with the domain that API applies to (Aspect Oriented Programming) then you will instantly understand how to use them. If every API is a new language then you are doing it wrong - the API should respect the conventions of both the computer language it is in, and the domain-specific terminology of the domain it serves.