diff options
| author | Marcin Chrzanowski <marcin.j.chrzanowski@gmail.com> | 2019-08-03 17:32:20 -0700 |
|---|---|---|
| committer | Marcin Chrzanowski <marcin.j.chrzanowski@gmail.com> | 2019-08-03 17:35:23 -0700 |
| commit | dc9f718ee41d5c91042c9e1790b4112c6d71f836 (patch) | |
| tree | 3b66803eb9378ccf569522270a728c737c3a579a | |
| parent | 4ade28116e367ebfba912b6ce7df620e93202e45 (diff) | |
Cleanup tags in post
| -rw-r--r-- | src/blog/polymorphism-in-solidity.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/blog/polymorphism-in-solidity.html b/src/blog/polymorphism-in-solidity.html index a6a6aca..9c55923 100644 --- a/src/blog/polymorphism-in-solidity.html +++ b/src/blog/polymorphism-in-solidity.html @@ -39,7 +39,7 @@ struct file { // ... }; </pre> -</a> +</p> <p> The important bit is the <code>f_op</code> field, of type <code>struct @@ -62,7 +62,6 @@ struct file_operations { // ... }; </pre> -</a> It's mostly a bunch of function pointers that appear to be... operations one might want to perform on a file. @@ -166,6 +165,7 @@ This doesn't look terrible yet. <p> Now imagine that you wanted to handle even more asset classes. +</p> <p> What if there was a token <code>YourToken</code> that had <code>mint</code> and |