# Why are FileHandle methods deprecated without warnings, and how do I show the warnings?

**URL:** <https://forums.swift.org/t/why-are-filehandle-methods-deprecated-without-warnings-and-how-do-i-show-the-warnings/53930>\
**Category:** Using Swift\
**Created:** [December 8, 2021, 8:05pm UTC](https://forums.swift.org/t/why-are-filehandle-methods-deprecated-without-warnings-and-how-do-i-show-the-warnings/53930 "2021-12-08T20:05:52Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![eskimo](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/eskimo/32/13558_2.png) [@eskimo](https://forums.swift.org/u/eskimo)\
**Post date:** [December 9, 2021, 10:39am UTC](https://forums.swift.org/t/why-are-filehandle-methods-deprecated-without-warnings-and-how-do-i-show-the-warnings/53930/3 "2021-12-09T10:39:23Z")

</div>

Just a point of clarification here:

> they can trigger exceptions, but aren't marked with `throw`

You’re comparing apples to oranges here. The exceptions thrown by these legacy APIs are Objective-C _language_ exceptions [1]. There are very different from Swift errors and Swift can’t deal with them at all. The Objective-C equivalent of a Swift error is an `NSError` output parameter.

Share and Enjoy

Quinn “The Eskimo!” @ DTS @ Apple

[1] On most platforms such exceptions are equivalent to C++ exceptions.

---

_[View the full topic](https://forums.swift.org/t/why-are-filehandle-methods-deprecated-without-warnings-and-how-do-i-show-the-warnings/53930)._