# Exception handling Published articles for Exception handling. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Exception Handling in Practice DevFeed: [Exception Handling in Practice]() Original publisher: [Read original article]() Author: Franco Fernando Published: 2026-08-28T05:50:28Z Content type: tutorial Language: en Sources: [The Polymathic Engineer]() Topics: [Exception](), [Code]() Tags: [code](), [exception](), [exception-handling](), [patterns]() ### AI overview An article about patterns and anti-patterns for signaling, catching, and surviving failures in code. ### Source excerpt Patterns and anti-patterns for signaling, catching, and surviving failures in your code. ## Coroutine Essentials DevFeed: [Coroutine Essentials]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2026-08-21T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Coroutines](), [Kotlin](), [coding](), [Software]() Tags: [async](), [cancellation](), [coding](), [concurrency](), [coroutine](), [coroutines](), [deferred](), [dispatcher](), [exception-handling](), [introduction](), [job](), [kotlin](), [launch](), [learn-to-program](), [parallelism](), [programming](), [runblocking](), [software](), [structured-concurrency](), [suspend-function](), [withcontext](), [yield]() ### AI overview This tutorial introduces essential Kotlin coroutine concepts for performing multiple tasks concurrently, such as making network calls while updating a screen. It aims to provide a foundation for day-to-day coding and more advanced coroutine concepts. ### Source excerpt When you're on hold during a phone call, you might also check your email. While brewing coffee, you might also cook breakfast. And while driving a car, you might listen to a podcast. In the same way, sometimes it's helpful for the software that we write to do more than one thing at a time. For example, it could make two or three network calls at one time--all while updating the screen to show the progress of each call. ## Wastrel Compiles Hoot Scheme-to-WebAssembly Output DevFeed: [Wastrel Compiles Hoot Scheme-to-WebAssembly Output]() Original publisher: [Read original article]() Author: Andy Wingo Published: 2026-03-31T20:34:23Z Content type: article Language: en Sources: [wingolog]() Topics: [WebAssembly](), [Compiler](), [scheme]() Tags: [accidentally-quadratic](), [aot](), [bigint](), [bignums](), [compiler](), [compilers](), [exception-handling](), [exceptions](), [gc](), [gcc](), [gmp](), [hoot](), [igalia](), [library](), [maps](), [precision](), [scheme](), [standard](), [tail-calls](), [wasm](), [wastrel](), [webassembly](), [whippet]() ### AI overview The article describes recent work on Wastrel, an ahead-of-time WebAssembly compiler, including compiling output from the Hoot Scheme-to-Wasm compiler. It covers implementing bignum operations with mini-gmp and updating Hoot to use standardized WebAssembly exception handling. ### Source excerpt Good day! Today (tonight), some notes on the last couple months of Wastrel, my ahead-of-time WebAssembly compiler. Back in the beginning of February, I showed Wastrel running programs that use garbage collection, using an embedded copy of the Whippet collector, specialized to the types present in the Wasm program. But, the two synthetic GC-using programs I tested on were just ported microbenchmarks, and didn't reflect the output of any real toolchain. In this cycle I worked on compiling the output from the Hoot Scheme-to-Wasm compiler. There were some interesting challenges! bignums When I originally wrote the Hoot compiler, it targetted the browser, which already has a bignum implementation in the form of BigInt, which I worked on back in the day. Hoot-generated Wasm files use host bigints via externref (though wrapped in structs to allow for hashing and identity). In Wastrel, then, I implemented the imports that implement bignum operations: addition, multiplication, and so on. I did so using mini-gmp, a stripped-down implementation of the workhorse GNU multi-precision library. At some point if bignums become important, this gives me the option to link to the full GMP instead. Bignums were the first managed data type in Wastrel that wasn't defined as part of the Wasm module itself, instead hiding behind externref, so I had to add a facility to allocate type codes to these "host" data types. More types will come in time: weak maps, ephemerons, and so on. I think bignums would be a great proposal for the Wasm standard, similar to stringref ideally (sniff!), possibly in an attenuated form. exception handling Hoot used to emit a pre-standardization form of exception handling, and hadn't gotten around to updating to the newer version that was standardized last July. I updated Hoot to emit the newer kind of exceptions, as it was easier to implement them in Wastrel that way. Some of the problems Chris Fallin contended with in Wasmtime don't apply in the Wastrel case: sinc ## From error-handling to structured concurrency DevFeed: [From error-handling to structured concurrency]() Original publisher: [Read original article]() Author: Nelson Elhage Published: 2026-03-23T15:30:00Z Content type: opinion Language: en Sources: [Nelson Elhage]() Topics: [Concurrency](), [Concurrent Programming](), [Error Handling](), [Exception]() Tags: [concurrency](), [error-handling](), [examples](), [exception](), [exception-handling](), [structured-concurrency]() ### AI overview This article examines how error-handling patterns based on stack unwinding and cleanup should be adapted for concurrent programs with multiple tasks. It introduces the problem of unhandled errors in concurrent execution and compares possible behaviors when one task fails. ### Source excerpt How should we think about error-handling in concurrent programs? In single-threaded programs, we've mostly converged on a standard pattern, with a diverse zoo of implementations and concrete patterns. When an error occurs, it is propagated up the stack until we find a stack frame which is prepared to handle it. As we do so, we unwind the stack frames in-order, giving each frame the opportunity to clean up or destroy resources as appropriate. ## Kotlin Coroutines Cancellation and Exception Handling DevFeed: [Kotlin Coroutines Cancellation and Exception Handling]() Original publisher: [Read original article]() Published: 2026-01-11T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [kotlin-coroutines](), [cancellation](), [Exception handling](), [Kotlin](), [Concurrency]() Tags: [cancellation](), [concurrency](), [coroutines](), [exception-handling](), [kotlin](), [kotlin-coroutines]() ### AI overview This article explains why cancellation and exception handling in Kotlin coroutines are difficult, emphasizing that the concepts are distinct but coupled. It discusses the flexibility and hidden complexity of the coroutine API and introduces explanations and best practices for learning and using these mechanisms. ### Source excerpt Cancellation and exception handling in coroutines is by far the most complex thing I've faced during my entire career. These two things are so complicated that I sometimes ask myself how people are using such a difficult-to-use framework. I read all the possible docs that I found, many different articles, video courses, and even tried to look at the code - and still, I feel that my understanding of this topic is quite bad. When reading articles, I often thought that their structure was not good and that things were not clarified in a reasonable way. Usually, articles are just a collection of examples that show how certain combinations of suspending functions or coroutine builders will work. Learning by examples is good, but they should help with understanding core concepts so that all other situations are easy to relate to what was learned. ## Simplifying Resource Management in mssql-python through Context Manager DevFeed: [Simplifying Resource Management in mssql-python through Context Manager]() Original publisher: [Read original article]() Author: Jahnvi Thakkar Published: 2025-09-26T09:49:51Z Content type: tutorial Language: en Sources: [Microsoft Python Engineering]() Topics: [Python](), [sql-server](), [Databases](), [Exception]() Tags: [azure](), [azure-sql](), [cleanup](), [client-driver](), [databases](), [exception-handling](), [python](), [python-driver-for-azure-sql](), [python-driver-for-sql-server](), [sql-server](), [sql-server-2025](), [transactions]() ### AI overview This tutorial explains context manager support in the mssql-python driver for Python applications using SQL Server and Azure SQL. It describes how context managers manage connections and cursors, commit successful transactions, roll back transactions when exceptions occur, and close connections automatically. ### Source excerpt Reviewed by: Sumit Sarabhai and Gaurav Sharma If you've worked with databases in Python, you know the boilerplate: open a connection, create a cursor, run queries, commit or rollback transactions, close cursors and connection. Forgetting just one cleanup step can lead to resource leaks (open connections) or even inconsistent data. That's where context managers step [...] The post Simplifying Resource Management in mssql-python through Context Manager appeared first on Microsoft for Python Developers Blog. ## ESP-IDF error handling in FreeRTOS-based embedded applications DevFeed: [ESP-IDF error handling in FreeRTOS-based embedded applications]() Original publisher: [Read original article]() Author: John Lee Published: 2025-08-19T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [C](), [Embedded Systems](), [Tutorial](), [Embedded Software Dev](), [real-time]() Tags: [blog](), [c](), [embedded](), [embedded-systems](), [error-handling](), [errors](), [esp-idf](), [esp32c3](), [exception-handling](), [freertos](), [logging](), [real-time](), [tutorial]() ### AI overview This tutorial explains error handling in FreeRTOS-based embedded systems. It reviews C techniques such as return codes and global error indicators, then introduces ESP-IDF's esp_err_t type and error-checking macros for more systematic error management. ### Source excerpt This article explains error handling in FreeRTOS-based embedded systems, highlighting common C practices and their limitations. It introduces ESP-IDF's esp_err_t type and error-checking macros, demonstrating how they help manage errors systematically. It shows practical ways to implement error handling in embedded applications. ## Finally, You Can Drop the Parentheses in Python 3.14 DevFeed: [Finally, You Can Drop the Parentheses in Python 3.14]() Original publisher: [Read original article]() Author: Abhimanyu Saharan Published: 2025-05-25T00:00:00Z Content type: article Language: en Sources: [Abhimanyu Saharan]() Topics: [Python 3.14](), [Exception](), [Python]() Tags: [exception](), [exception-handling](), [python](), [python-3-14]() ### AI overview Python 3.14 introduces a cleaner syntax for catching multiple exceptions by allowing the parentheses to be omitted, as specified in PEP 758. ### Source excerpt Python 3.14 simplifies exception handling with PEP 758, letting you drop parentheses when catching multiple exceptions, cleaner, consistent, and backward-safe. ## Coroutines Mastery DevFeed: [Coroutines Mastery]() Original publisher: [Read original article]() Published: 2025-05-23T00:00:00Z Content type: article Language: en Sources: [Kt. Academy]() Topics: [kotlin-coroutines](), [Kotlin](), [Exception handling](), [Concurrency](), [debugging](), [Testing](), [Android](), [Back end]() Tags: [2025](), [android](), [backend](), [coroutines](), [debugging](), [exception-handling](), [kotlin](), [kotlin-coroutines](), [testing](), [workshop](), [workshop-learning-programming]() ### AI overview Coroutines Mastery is a five-week, self-paced Kotlin Coroutines course with video lessons, exercises, twice-weekly live Q&A sessions, and platform discussions. It covers topics including debugging, testing, exception handling, and synchronization issues, and is intended for Kotlin Coroutines users from beginners to advanced developers. ### Source excerpt 5-weeks-long kohort workshop to master Kotlin Coroutines. ## Kotlin Exception Handling: Why Singleton Exceptions are a bad idea DevFeed: [Kotlin Exception Handling: Why Singleton Exceptions are a bad idea]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2024-09-18T12:56:49Z Content type: tutorial Language: en Sources: [Shreyas Patil's Blog]() Topics: [Exception](), [Kotlin](), [debugging](), [App](), [Crashlytics]() Tags: [android](), [best-practices](), [coding](), [crashlytics](), [debugging](), [errors](), [exception-handling](), [exceptionhandling](), [exceptions](), [java](), [jvm](), [kotlin](), [kotlin-beginner](), [kotlin-multiplatform](), [mistakes](), [programming-blogs](), [programming-tips]() ### AI overview This Kotlin micro-blog explains why singleton exception instances can produce incorrect stack traces and mislead debugging. It recommends avoiding singleton exceptions when stack traces matter, while noting they may be acceptable for internal state or informational exceptions that are not monitored at scale. ### Source excerpt Understand why using singleton exceptions in Kotlin can be a bad practice and how it affects stack traces and debugging in your applications. ## Handling Runtime Exceptions DevFeed: [Handling Runtime Exceptions]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2024-02-28T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Exception](), [Kotlin](), [Code]() Tags: [custom-exceptions](), [exception](), [exception-handling](), [exception-types-in-kotlin](), [exceptions](), [how-to](), [introduction](), [kotlin](), [kotlin-programming](), [kotlin-throw-keyword](), [learn-to-program](), [programming](), [runtime-errors](), [try-catch-blocks]() ### AI overview This Kotlin tutorial explains runtime exceptions, contrasting runtime problems with compile-time errors and introducing how to handle unexpected problems while a program runs. ### Source excerpt In real life, when we decide to do something, we primarily think in terms of a successful experience. For example, if you're driving to your friend's house for dinner, you might look up the directions on a mapping app, make sure you've got enough gasoline in the car, and leave at the right time in order to arrive when dinner is hot. If everything goes according to plan, you'll arrive on time. ## Exceptional Exception Handling DevFeed: [Exceptional Exception Handling]() Original publisher: [Read original article]() Author: Google Testing Bloggers (noreply@blogger.com) Published: 2023-12-05T13:19:00Z Content type: tutorial Language: en Sources: [Google Testing Blog]() Topics: [Exception](), [Java](), [debugging](), [Code]() Tags: [code](), [code-health](), [debugging](), [exception-handling](), [exceptions](), [java](), [tott](), [yiming-sun]() ### AI overview This article explains how oversized exception-handling blocks can obscure program logic, catch unintended exceptions, and lose root-cause information. Using Java examples, it recommends narrowing the try block, catching the specific exception, and preserving the original cause when rethrowing. ### Source excerpt This is another post in our Code Health series. A version of this post originally appeared in Google bathrooms worldwide as a Google Testing on the Toilet episode. You can download a printer-friendly version to display in your office. by Yiming Sun Have you ever seen huge exception-handling blocks? Here is an example in Java, although you may have seen similar problems in Python, TypeScript, Kotlin, or any language that supports exceptions. Let's assume we are calling bakePizza() to bake a pizza, and it can be overbaked, throwing a PizzaOverbakedException. class PizzaOverbakedException extends Exception {}; void bakePizza () throws PizzaOverbakedException {}; try { // 100+ lines of code to prepare pizza ingredients. ... bakePizza(); // Another 100+ lines of code to deliver pizza to a customer. ... } catch (Exception e) { throw new IllegalStateException(); // Root cause ignored while throwing new exception. } Here are the problems with the above code: Obscuring the logic. The method bakePizza(), is obscured by the additional lines of code of preparation and delivery, so unintended exceptions from preparation and delivery may be caught. Catching the general exception. catch (Exception e) will catch everything, despite that we might only want to handle PizzaOverbakedException here. Rethrowing a general exception, with the original exception ignored. This means that the root cause is lost - we don't know what exactly goes wrong with pizza baking while debugging. Here is a better alternative, rewritten to avoid the problems above. class PizzaOverbakedException extends Exception {}; void bakePizza () throws PizzaOverbakedException {}; // 100+ lines of code to prepare pizza ingredients. ... try { bakePizza(); } catch (PizzaOverbakedException e) { // Other exceptions won't be caught. // Rethrow a more meaningful exception; so that we know pizza is overbaked. throw new IllegalStateException("You burned the pizza!", e); } // Another 100+ lines of code to deliver pizza to a cu ## I know Nothing in Kotlin DevFeed: [I know Nothing in Kotlin]() Original publisher: [Read original article]() Author: Colin Lee Published: 2022-09-16T15:32:41Z Content type: tutorial Language: en Sources: [Making Meetup - Medium]() Topics: [Kotlin](), [Exception](), [multiplatform](), [Coroutines](), [iOS](), [Swift]() Tags: [coroutines](), [dns](), [exception](), [exception-handling](), [ios](), [kotlin](), [kotlin-multiplatform-mobile](), [network](), [nothing](), [refactor](), [swift](), [timeout]() ### AI overview This article explains Kotlin's Nothing type through a code-pairing example involving repository calls in a shared Kotlin Multiplatform Mobile module. It describes refactoring repeated exception handling, rethrowing CancellationExceptions for cooperative coroutine cancellation, and using Nothing for functions that always throw. ### Source excerpt When the Greek philosopher Socrates professed that "I know only one thing -- that I know nothing," he wasn't exactly professing ignorance. It was an ancient formulation of the Dunning-Kruger effect. He had discovered that the more he learned, the wider the expanse of human knowledge seemed and the less that it seemed he knew. A fool, on the other hand, might believe that they're "not smart, but genius... and a very stable genius at that," and that they know "only the best words." In this sense, it's a good thing to know nothing. It's also true in Kotlin. During a recent code pairing session, I discovered that in Kotlin, there are numerous developers who have written code in the language for many years. And yet, they still don't know Nothing. Our pairing session became a big fuss about Nothing. We were working on some Repository code in our shared Kotlin Multiplatform Mobile (KMM) module of our Meetup for Organizers app. In this code, there was a repeated block at the end of every repository call to handle network, DNS, and timeout errors. We decided it would make sense to refactor this block into a function as we used it so often. The repeated block in question handled a catch block. It had to re-throw any CancellationExceptions to allow cooperative cancellation of coroutines. Then we had to wrap any other exception and re-throw it as a custom exception type so that we can easily tell iOS a complete list of all types we intend to throw in a @Throws declaration. This allows exception handling and avoids crashing when our functions are called by Swift code. In essence, this code block always threw an Exception. The pairing session became quite funny, like the Laurel and Hardy "Who's on First" comedy routine, but you could tell there was Nothing more frustrating, too. It went something like this: "Why am I getting this red text at the call site?" "The return type is incorrect because you always throw an exception. You need to return Nothing." "I already am returning nothi ## I Know Nothing in Kotlin DevFeed: [I Know Nothing in Kotlin]() Original publisher: [Read original article]() Published: 2022-08-30T17:52:35Z Content type: tutorial Language: en Sources: [Colin The Shots]() Topics: [Kotlin](), [Exception](), [Coroutines](), [kotlin multiplatform mobile]() Tags: [coroutines](), [exception-handling](), [kotlin](), [kotlin-multiplatform-mobile](), [refactor]() ### AI overview This developer article explains Kotlin's Nothing type through a refactoring example involving exception handling in a shared Kotlin Multiplatform Mobile repository. It distinguishes Nothing from Unit and describes using it when a function always throws, including when interoperating with Swift code and preserving coroutine cancellation. ### Source excerpt When the Greek philosopher Socrates professed that "I know only one thing-- that I know nothing," he wasn't exactly professing ignorance. It was an ancient formulation of the Dunning-Kruger effect. ## Making unwinding through JIT-ed code scalable - Optimistic Lock Coupling DevFeed: [Making unwinding through JIT-ed code scalable - Optimistic Lock Coupling]() Original publisher: [Read original article]() Author: Thomas Neumann (noreply@blogger.com) Published: 2022-06-26T08:52:00Z Content type: article Language: en Sources: [Database Architects]() Topics: [Exception](), [Data structures](), [Concurrency]() Tags: [code](), [data-structure](), [exception](), [exception-handling](), [locking](), [mutex](), [performance](), [set]() ### AI overview The article explains a scalable approach to unwinding through JIT-ed code using a read-optimized B-tree with optimistic lock coupling. Writers use conventional exclusive lock coupling, while readers use version locks and validate their reads so they can run in parallel when writes are uncommon. ### Source excerpt This article is part of the series about scalable unwinding that starts here. When thinking about exception handling it is reasonable to assume that we will have far more unwinding requests than changes to the unwinding tables. In our setup, the tables only change when JITed code is added to or removed from the program. That is always expensive to begin with due the mprotect calls, TLB shootdowns, etc. Thus we can safely assume that we will have at most a few hundred updates per second even in extreme cases, probably far less. Lookups however can easily reach thousands or even millions per second, as we do one lookup per frame. This motivates us to use a read-optimized data structure, a b-tree with optimistic lock coupling: Writers use traditional lock coupling (lock parent node exclusive, lock child node exclusive, release parent node, lock child of child, etc.), which works fine as long as there is not too much contention. Readers however have to do something else, as we expect thousands of them. One might be tempted to use a rw-lock for readers, but that does not help. Locking an rw-lock in shared mode causes an atomic write, which makes the threads fight over the cache line of the lock even if there is no (logical) contention. Instead, we use version locks, where readers do no write at all: // Common logic for version locks struct version_lock { // The lock itself. The lowest bit indicates an exclusive lock, // the second bit indicates waiting threads. All other bits are // used as counter to recognize changes. // Overflows are okay here, we must only prevent overflow to the // same value within one lock_optimistic/validate // range. Even on 32 bit platforms that would require 1 billion // frame registrations within the time span of a few assembler // instructions. uintptr_t version_lock; }; #ifdef __GTHREAD_HAS_COND // We should never get contention within the tree as it rarely changes. // But if we ever do get contention we use these for waiting static __gthre ## In-Process Patchless AMSI Bypass DevFeed: [In-Process Patchless AMSI Bypass]() Original publisher: [Read original article]() Author: CCob Published: 2022-04-17T16:30:25Z Content type: tutorial Language: en Sources: [Ethical Chaos]() Topics: [Windows](), [Exception](), [exceptions](), [debug](), [C2](), [Processes]() Tags: [article](), [breakpoint](), [bypass](), [c2](), [context](), [debugger](), [edr](), [exception](), [exception-handling](), [execution](), [extension](), [windows]() ### AI overview This article explains an in-process, patchless AMSI bypass approach using vectored exception handling. It contrasts this technique with SharpBlock's debugger-based child-process method and describes manipulating thread context at the point an exception occurs. ### Source excerpt Some of you may remember my patchless AMSI bypass article and how it was used inside SharpBlock to bypass AMSI on the child process that SharpBlock spawns. This is all well a good when up against client environments that are not too sensitive to the fork and run post exploitation model of operating. What about [...] The post In-Process Patchless AMSI Bypass appeared first on Ethical Chaos. ## Kotlin Coroutines Exception Handling Cheat Sheet DevFeed: [Kotlin Coroutines Exception Handling Cheat Sheet]() Original publisher: [Read original article]() Author: Lukas Lechner Published: 2020-10-28T14:12:43Z Content type: article Language: en Sources: [Lukas Lechner]() Topics: [Coroutines](), [Exception](), [kotlin-coroutines](), [Kotlin]() Tags: [allgemein](), [allgemein-kotlin](), [cheat-sheet](), [coroutines](), [exception](), [exception-handling](), [kotlin](), [kotlin-coroutines]() ### AI overview A cheat sheet explains six key points about exception handling in Kotlin coroutines, including try-catch handling, exception propagation through job hierarchies, differences between launch and async, coroutineScope behavior, and cancellation exceptions. ### Source excerpt Exception Handling with Kotlin Coroutines is hard. I wrote an extensive article about it and gave talks about it at several conferences. Some developers suggested creating some kind of cheat sheet that could be helpful for implementing appropriate exception handling in coroutine-based code. Here it is 😉. It contains the six most important points. You Read More The post Kotlin Coroutines Exception Handling Cheat Sheet first appeared on Lukas Lechner. ## Kotlin and Exceptions DevFeed: [Kotlin and Exceptions]() Original publisher: [Read original article]() Author: Roman Elizarov Published: 2020-06-10T08:18:06Z Content type: article Language: en Sources: [Stories by Roman Elizarov on Medium]() Topics: [Exception](), [Kotlin](), [Java](), [Error Handling](), [Code]() Tags: [api-design](), [code](), [error-handling](), [exception-handling](), [exceptions](), [java](), [kotlin](), [programming]() ### AI overview The article examines Kotlin exceptions by tracing their origins to Java checked exceptions. It explains how checked exceptions were intended to reduce missed error checks, then discusses problems including boilerplate, overly broad API declarations, ignored exceptions, and poor compatibility with Java 8 lambdas and streams. ### Source excerpt Photo by John Mark Arnold on Unsplash What are Kotlin Exceptions and how should you use them? To figure it out let's look at their origins first. Exceptions came to Kotlin from Java. The story with exceptions in Java is complicated, though. I'll give a brief overview. The Origin Java has a unique concept of checked exceptions that were designed to solve the problem of verbose and error-prone error-handling (pun intended). In languages predating Java, like in venerable C, you have to write code like shown in this snippet when doing basic input/output: file = fopen("file.txt", "r"); if (file == NULL) { // handle error & return } // work with file, check for error after each file operation Every time you perform an operation that might fail due to some external circumstance, which happens especially often with files and network, you have to write code that checks the corresponding error condition and handles it. That's tedious, easy to forget, hard to debug. Java set on a noble goal to eliminate this problem. The solution was to use checked exceptions. Every file I/O operation is declared as throws IOException in Java and the compiler checks that you either handle it or declare that you rethrow it. The beauty of this is that you can write exception-handling code once for a whole bunch of I/O operations and you cannot forget writing it since the Java compiler is there to help you. file = FileInputStream("file.txt"); // throws IOException No error-handling boilerplate, no more missed error checks. It was such a bliss to program in Java... for a while. Problems Problems with checked exceptions accumulated over the years. Memory input/output APIs like ByteArrayInputStream were still declared to throw IOException that you had to handle even though it never happened, people abused checked exceptions in API design leading to long, contagious lists of thrown exceptions, developers routinely caught and ignored checked exceptions just to fit some exception-throwing API under an in ## Functional Hangman in Kotlin with Arrow (part 2) DevFeed: [Functional Hangman in Kotlin with Arrow (part 2)]() Original publisher: [Read original article]() Author: Stojan Anastasov Published: 2018-12-25T00:00:00Z Content type: tutorial Language: en Sources: [Stojan Anastasov's blog]() Topics: [Kotlin](), [Programming](), [IO](), [Error Handling]() Tags: [arrowkt](), [code](), [error-handling](), [exception-handling](), [fp](), [functional](), [io](), [kotlin]() ### AI overview This tutorial explains the second part of converting a functional Hangman game from Scala with ZIO to Kotlin with Arrow. It replaces a hard-coded IO data type with a polymorphic design using Kind and introduces MonadDefer to represent capabilities such as lazy evaluation, exception handling, and completion with a result. ### Source excerpt Converting a Functional Hangman game from Scala (ZIO) to Kotlin (with Arrow) was a nice exercise. I enjoyed working on it and I learned a lot. When I asked for feedback on the #arrow channel, one of the maintainers, Leandro had an interesting suggestion. Instead of hard-coding the data type IO I should try and make the program polymorphic and use Kind instead. That means writing the code focusing on the domain logic, using abstractions, and deferring the decision for the concrete data type like IO or Single (from RxJava) until the main function. The journey I was not familiar with that style of programming so I used this example from the excellent Arrow documentation as a guide. Writing to the the console In the previous article I used IO to interact with the console. IO represents an operation that can be executed lazily, fail with an exception (the exception is captured inside IO), run forever or return a single A. Let's take a look at the original implementation: fun putStrLn(line: String): IO = IO { println(line) } // Usage in main() putStrLn("Hello world!").unsafeRunSync() putStrLn is a function that take a String and return a IO. IO takes a lambda that is lazily evaluated at the end of the world, when we call unsafeRunSync(). If we want to achieve the same thing with Single we could use Single.fromCallable wrap our lambda and evaluate it in the main function when we call subscribe(). fun putStrLn(line: String): Single = Single.fromCallable { println(line) } // Usage in main() putStrLn("Hello World").subscribe() Here bothIO and Single have something in common. A set of capabilities like: lazy evaluation, exception handling, and running forever or completing with a result of type A. IO and Single do a lot more, but for this use case, we want something as simple as possible that has the same capabilities. There is a type-class in Arrow that can do just that and it's called MonadDefer(more info). After a few iterations, and feedback from th ## Debugger data model, Javascript & x64 exception handling DevFeed: [Debugger data model, Javascript & x64 exception handling]() Original publisher: [Read original article]() Author: Axel "0vercl0k" Souchet Published: 2017-12-01T14:59:00Z Content type: tutorial Language: en Sources: [Diary of a reverse-engineer]() Topics: [debugging](), [JavaScript](), [Exception handling](), [Microsoft](), [Tooling](), [Reverse Engineering]() Tags: [debugging](), [debugging-tools](), [exception](), [exception-handling](), [javascript](), [microsoft](), [reverse-engineering](), [seh](), [time-travel-debugging](), [ttd](), [windbg]() ### AI overview This tutorial explores the WinDbg Preview debugger data model, JavaScript extensions, and Microsoft's time travel debugging tools. It explains how these features can be used to enumerate x64 try/except handlers in JavaScript. ### Source excerpt Introduction The main goal of today's post is to show a bit more of what is now possible with the latest Windbg (currently branded "WinDbg Preview" in the Microsoft store) and the time travel debugging tools that Microsoft released a few months ago. When these finally got released, a bit ... ## Working With APIs the Pythonic Way DevFeed: [Working With APIs the Pythonic Way]() Original publisher: [Read original article]() Author: Haki Benita Published: 2017-01-04T22:00:00Z Content type: tutorial Language: en Sources: [Haki Benita]() Topics: [API](), [Python](), [Exception](), [data]() Tags: [apis](), [articles](), [data-structure](), [django](), [exception-handling](), [http](), [implementation](), [logging](), [python](), [testing]() ### AI overview A step-by-step tutorial on building a Python module for communicating with an external payment gateway. It covers handling HTTP and remote payment errors, defining custom exceptions, logging, and returning structured charge responses with namedtuple. ### Source excerpt Communication with external services is an integral part of any modern system. Whether it's a payment service, authentication, analytics or an internal one - systems need to talk to each other. In this short article we are going to implement a module for communicating with a made-up payment gateway, step by step. ## Checked vs. Unchecked Exceptions in Java: A Historical Perspective and Comparison DevFeed: [Checked vs. Unchecked Exceptions in Java: A Historical Perspective and Comparison]() Original publisher: [Read original article]() Author: umer Published: 2016-04-02T00:00:00Z Content type: tutorial Language: en Sources: [Code Ahoy - Articles]() Topics: [Exception](), [Java](), [Error Handling](), [Programming](), [C](), [Lisp]() Tags: [c](), [error-handling](), [exception-handling](), [exceptions](), [java](), [lisp]() ### AI overview A tutorial for new Java developers that explains the historical motivation for Java's exception-handling mechanism and examines the debate between checked and unchecked exceptions, contrasting them with error-code patterns in C. ### Source excerpt This blog post is intended for new Java developers. It starts with a historical perspective and a look at what motivated the design and creation of Java's exception handling mechanism. It also explores the hotly debated checked vs unchecked exceptions debate with some personal insights. Let's start. Historical Perspective Back in the time of the "C" programming language, it was customary to return values such as -1 or NULL from functions to indicate errors. This was practical for small applications but didn't scale well for larger applications - developers had to check and track every possible return value: a return value of 2 might indicate "host is down" error in library A whereas in library B, it could mean "illegal filename". Although, developers tried to fix this and attempts were made to standardize error codes by setting global variables, but it didn't help much. #define ENOENT 2 /* No such file or directory */ #define ESRCH 3 /* No such process */ #define EINTR 4 /* Interrupted system call */ #define EIO 5 /* I/O error */ #define ENXIO 6 /* No such device or address */ #define E2BIG 7 /* Argument list too long */ #define ENOEXEC 8 /* Exec format error */ #define EBADF 9 /* Bad file number */ #define ECHILD 10 /* No child processes */ #define EAGAIN 11 /* Try again */ #define ENOMEM 12 /* Out of memory */ James Gosling and other designers felt that a similar approach would go against the design goals of Java programming language. They wanted: a cleaner, robust and portable approach built-in language support for error checking and handling. Essentially, one of their main design goals was to build a language that's robust and able to cope with errors during execution or at least recognize when going go wrong. This principle is at the core of Java's error handling design, as we'll see later. James Gosling explains in one of his interviews: One of the traditional things to screw up in C code is opening a data file to read. It's semi-traditional in the C world to ## Handling crashes on Mac OS X: ordering of Mach exceptions versus POSIX signals DevFeed: [Handling crashes on Mac OS X: ordering of Mach exceptions versus POSIX signals]() Original publisher: [Read original article]() Author: Mark Seaborn (noreply@blogger.com) Published: 2013-08-07T20:25:00Z Content type: tutorial Language: en Sources: [Mark Seaborn]() Topics: [Operating system](), [Kernel](), [Processes](), [Exception](), [POSIX](), [out-of-process](), [Remote Procedure Call (RPC)]() Tags: [crash](), [dialog](), [exception](), [exception-handling](), [experimentation](), [handler](), [kernel](), [mac](), [mac-os](), [memory](), [ordering](), [os](), [out-of-process](), [posix](), [process](), [processes](), [rpc](), [signal]() ### AI overview This article explains how Mac OS X handles hardware exceptions through POSIX signals and Mach exceptions. It reports that Mach exception handlers receive priority, while the kernel uses a first-chance Mach handler, a POSIX signal handler, and a second-chance Mach handler when handling faults and crashes. ### Source excerpt Mac OS X is a curious operating system because its kernel is derived from two kernel codebases -- the Mach kernel and a BSD kernel -- that have been glued together. From these two ancestors, OS X inherits two different mechanisms for processes to handle hardware exceptions (a.k.a. faults): POSIX signals: In-process only. Registered per-process. The handler is always called on the thread that produced the fault. Mach exceptions: Allow both in-process and out-of-process handling. Can be registered per-thread and per-process. The handler is invoked via Mach RPC. On OS X, it's possible for a process to have both POSIX signal handlers and Mach exception handlers registered. It's not immediately obvious which of the two handlers will take priority and get invoked first, but experimentation shows that it's the Mach handler. If a process faults with a memory access error, the Mach exception handler for EXC_BAD_ACCESS gets invoked first, and if this handler returns KERN_FAILURE, the POSIX signal handler for SIGBUS will then be invoked. However, that's not the full story. OS X has a built-in Crash Reporter service which will create a crash dump if an application crashes and pop up a dialog box. Crash Reporter works via Mach exception handling and runs out-of-process. An application will normally have Crash Reporter's crash handler registered as one of its default Mach exception handlers. But what stops this handler from interfering with normal use of POSIX signals, if Mach exception handlers take priority over POSIX signals? The answer is that OS X's kernel has three steps for handling a hardware exception: First-chance Mach exception handler: The kernel tries to invoke the Mach exception handler registered for the type of fault that occurred, e.g. EXC_BAD_ACCESS. If there's no handler registered, it skips this step. If the handler returns KERN_SUCCESS, the kernel resumes the thread that faulted. POSIX signal handler: If the Mach exception handler was absent or returned KERN_ ## C++ Name Mangling and Compiler ABI Compatibility DevFeed: [C++ Name Mangling and Compiler ABI Compatibility]() Original publisher: [Read original article]() Published: 2011-03-14T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [C++](), [Compiler](), [Specifications](), [Exception](), [ReactOS]() Tags: [c-plus-plus](), [code](), [compiler](), [exception](), [exception-handling](), [free](), [open-source](), [os](), [react](), [reactos](), [specifications](), [win32](), [winapi]() ### AI overview The article explains how C++ compilers handle name mangling and exception handling, noting that these behaviors are not fully specified by the C++ standard. It describes compatibility problems when linking code built with different compilers or compiler versions, including differences between GCC, Visual Studio, and other toolchains. ### Source excerpt C++ Mangling Those with any experience using third party libraries while writing C++ applications should quickly recognize the topic I am about to go over and can skip down to paragraph three for the ReactOS specific miseries. Those that are not familiar with the issues or want a refresher should continue. The C++ standard outlines behavior for C++ code when compiled. To be considered a compliant compiler requires following the specifications laid out, though no compiler that I am aware of actually implements 100% of the entire standard. [Next page]()