michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-16 22:37:49 +00:00
Code Issues Projects Releases Wiki Activity

Fix wording

Browse Source
This commit is contained in:
Philipp Oppermann
2015-10-23 13:03:58 +02:00
parent 29fa352663
commit cad0065e74
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
_posts/2015-10-23-printing-to-screen.md
View File

@@ -248,7 +248,7 @@ fn clear_row(&mut self, row: usize) {
} }
``` ```
## Providing an Interface/Printing from outside/Synchronization/... ## Providing an Interface
To provide a global writer that can used as an interface from other modules, we can add a `static` writer: To provide a global writer that can used as an interface from other modules, we can add a `static` writer:
```rust ```rust
@@ -259,7 +259,7 @@ pub static WRITER: Writer = Writer {
}; };
``` ```
This won't work! You can try it yourself in the `print_something` function. The reason is that we try to take a mutable reference (`&mut`) to a immutable `static` when calling `WRITER.print_byte`. But we can't use it to print anything! You can try it yourself in the `print_something` function. The reason is that we try to take a mutable reference (`&mut`) to a immutable `static` when calling `WRITER.print_byte`.
To resolve it, we could use a [mutable static]. But then every read and write to it would be unsafe since it could easily introduce data races and other bad things. Using `static mut` is highly discouraged, there are even proposals to [remove it][remove static mut]. To resolve it, we could use a [mutable static]. But then every read and write to it would be unsafe since it could easily introduce data races and other bad things. Using `static mut` is highly discouraged, there are even proposals to [remove it][remove static mut].