October 2024
Intermediate to advanced
270 pages
8h 13m
Spanish
Content preview from 97 cosas que todo programador Java debe saber
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Capítulo 37. Interoperabilidad con Kotlin
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
Sebastiano Poggi
En los últimos años, Kotlin ha sido un tema candente en la comunidad JVM; el uso del lenguaje aumenta constantemente, desde proyectos móviles a backend. Una de las ventajas de Kotlin es su gran interoperabilidad con Java desde el primer momento.
Llamar a cualquier código Java desde Kotlin simplemente funciona. Kotlin entiende Java perfectamente bien, pero hay una pequeña molestia que puede presentarse si no sigues las buenas prácticas de Java al pie de la letra: la falta de tipos no anulables en Java. Si no aplicas anotaciones de anulabilidad en Java, Kotlin asume que todos esos tipos tienen anulabilidad desconocida: son los llamados tipos de plataforma . Si estás seguro de que nunca serán null, puedes coaccionarlos a un tipo nonull con el operador !! o casteándolos a un tipo nonull. En cualquier caso, si el valor es null en tiempo de ejecución, se producirá un fallo. La mejor manera de manejar este escenario es añadir anotaciones de anulabilidad como @Nullable y @NotNull a tus API Java. Hay una gran variedad de anotaciones compatibles: JetBrains, Android, JSR-305, FindBugs y otras. De este modo, Kotlin conocerá la anulabilidad del tipo, y cuando codifiques en Java recibirás información adicional del IDE ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.