29.xhtml 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!--
  3. h t t :: / / t /
  4. h t t :: // // t //
  5. h ttttt ttttt ppppp sssss // // y y sssss ttttt //
  6. hhhh t t p p s // // y y s t //
  7. h hh t t ppppp sssss // // yyyyy sssss t //
  8. h h t t p s :: / / y .. s t .. /
  9. h h t t p sssss :: / / yyyyy .. sssss t .. /
  10. <https://y.st./>
  11. Copyright © 2016 Alex Yst <mailto:copyright@y.st>
  12. This program is free software: you can redistribute it and/or modify
  13. it under the terms of the GNU General Public License as published by
  14. the Free Software Foundation, either version 3 of the License, or
  15. (at your option) any later version.
  16. This program is distributed in the hope that it will be useful,
  17. but WITHOUT ANY WARRANTY; without even the implied warranty of
  18. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  19. GNU General Public License for more details.
  20. You should have received a copy of the GNU General Public License
  21. along with this program. If not, see <https://www.gnu.org./licenses/>.
  22. -->
  23. <!DOCTYPE html>
  24. <html xmlns="http://www.w3.org/1999/xhtml">
  25. <head>
  26. <base href="https://y.st./en/weblog/2016/03-March/29.xhtml" />
  27. <title>There is no way to win with her &lt;https://y.st./en/weblog/2016/03-March/29.xhtml&gt;</title>
  28. <link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
  29. <link rel="stylesheet" type="text/css" href="/link/basic.css" />
  30. <link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
  31. <script type="text/javascript" src="/script/javascript.js" />
  32. <meta name="viewport" content="width=device-width" />
  33. </head>
  34. <body>
  35. <nav>
  36. <p>
  37. <a href="/en/">Home</a> |
  38. <a href="/en/a/about.xhtml">About</a> |
  39. <a href="/en/a/contact.xhtml">Contact</a> |
  40. <a href="/a/canary.txt">Canary</a> |
  41. <a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
  42. <a href="/en/opinion/">Opinions</a> |
  43. <a href="/en/coursework/">Coursework</a> |
  44. <a href="/en/law/">Law</a> |
  45. <a href="/en/a/links.xhtml">Links</a> |
  46. <a href="/en/weblog/2016/03-March/29.xhtml.asc">{this page}.asc</a>
  47. </p>
  48. <hr/>
  49. <p>
  50. Weblog index:
  51. <a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
  52. <a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
  53. <a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
  54. </p>
  55. <hr/>
  56. <p>
  57. Jump to entry:
  58. <a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
  59. <a rel="prev" href="/en/weblog/2016/03-March/28.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/03-March/30.xhtml">Next&gt;</a>
  61. <a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
  62. </p>
  63. <hr/>
  64. </nav>
  65. <header>
  66. <h1>There is no way to win with her</h1>
  67. <p>Day 00388: Tuesday, 2016 March 29</p>
  68. </header>
  69. <p>
  70. My mother has come to the conclusion that my journal is an attack on her, and that I write in it only so use against her.
  71. First of all, most of the content of my journal has nothing to do with her.
  72. Second, I wasn&apos;t trying to attack her yesterday with the entry I found, I was trying to defend myself! I swear, she&apos;s more paranoid than even I am in some ways.
  73. Next, she was insisting that I may have told her, but that I hadn&apos;t gotten her attention, so she didn&apos;t hear.
  74. I said nothing until she pressured for more information about the entry, at which point I explained that it said that she had come in to take a look at it.
  75. At that point, she said that she may have taken a look at it but had been too stressed to remember.
  76. She was still taking my recording of the event to be an attack though.
  77. I promised that I wouldn&apos;t bring up passages from my journal again to her, then asked if I could have her sign off that I&apos;d told her things if I asked her too.
  78. She said that the only thing that she&apos;d sign if i asked for her to sign off on having been told is an eviction notice.
  79. In other words, I&apos;m not allowed to defend myself whatsoever.
  80. Whatever she says happened goes, even if she&apos;s dead wrong.
  81. Likewise, she told me off for standing up for Vanessa, which I often do when mother has screwy ideas in her head and is telling Vanessa off for no good reason.
  82. Apparently, I can&apos;t defend my sister either, as defending is interpreted as an attack against the attacking party, our mother.
  83. This living situation is horrid, and I need to get myself out of it.
  84. I need to find a job and move out.
  85. </p>
  86. <p>
  87. I spent the productive part of my day visiting what I thought were the local offices of my dentist.
  88. I looked up the addresses again online before heading out, finding three locations in North Bend, and found that I was on the correct website yesterday when I saw the Virginia Avenue address.
  89. However, that address doesn&apos;t actually have an office run by my dental health provider.
  90. While I was looking for Advantage Dental, this office was run by Above Dental.
  91. Furthermore, the location will soon be run by Apple Dental, which again, isn&apos;t Advantage dental.
  92. So why does Advantage Dental have this address listed as one of their offices? The second location was the one that I&apos;d visited yesterday, so I passed it by.
  93. The third location was also not actually an Advantage Dental office.
  94. This time, the office was owned by the Woodland Dental Clinic.
  95. Why in the world are two out of the three Advantage Dental locations listed on the Advantage Dental clinic not actually Advantage Dental locations? After I explained the situation, aside from the fact that I was trying to get an earlier appointment by visiting several locations, the woman at the Woodland Dental Clinic called the Advantage looked me up on her computer.
  96. Apparently, the Woodland Dental Clinic and Advantage Dental are either on the same computer system or can at least retrieve information from each other&apos;s systems.
  97. Maybe all the local dental practices can do that.
  98. In any case, even after having spoken directly with an Advantage Dental representative in person yesterday about setting up an appointment at the local office, The Coos Bay office was listed as being the one that I was supposed to visit, so the woman at the Woodland Dental Clinic telephoned Advantage Dental and got that cleared up.
  99. I think at this point, it might be a bad idea to try getting an appointment at the original Coos Bay location, so I gave up on that plan.
  100. On the way home, I walked into the local office and set up my appointment there.
  101. On May 23, I will see the dentist if we are still in the area.
  102. </p>
  103. <p>
  104. My mother asked how my tooth was doing, so I told her that it was fine.
  105. The fact is, it wasn&apos;t hurting at the moment.
  106. The pain comes and goes.
  107. She interpreted this to mean that I had somehow managed to kill the tooth, so it wasn&apos;t going to feel pain any more.
  108. I&apos;m not even going to bother trying to set her strait on that.
  109. She seems very much of the opinion that the pain is one of the main problems with the damaged tooth, but I disagree.
  110. The pain is a warning of the problem.
  111. With her thinking that it&apos;s done hurting though, maybe she&apos;ll worry less.
  112. Additionally, maybe she will just forget about or drop her plan to have me try lying to the dentists.
  113. It was stupid of me to tell her about the toothache in the first place.
  114. I need to learn to keep my mouth shut.
  115. </p>
  116. <p>
  117. I decided not to use either of the data-packing schemes that I came up with for exception codes yesterday.
  118. The problem with them is that they don&apos;t make full use of the thirty-two bit integer range.
  119. Some thirty-two bit integers wouldn&apos;t translate to actual information.
  120. It&apos;s already the case that most sixty-four bit integers won&apos;t translate to error strings, but that&apos;s just the cost of making my code compatible with thirty-two bit platforms.
  121. I shouldn&apos;t waste what space I have in the thirty-two bit range though.
  122. Additionally, translating the thirty-two bit integer back into a readable error code on a thirty-two bit platform while using a twenty-three or forty character character set seems like a nearly impossible task without the <abbr title="GNU Multiple Precision Arithmetic Library">GMP</abbr> extension.
  123. If I use a character set that allows me to break the integer directly on lines between bits, the task becomes much more manageable.
  124. Now I just needed to decide what size I want my character set to be.
  125. Any remaining bits left over that can&apos;t be translated into full characters can be used to store binary flags of some sort.
  126. Using four-bit bit characters, I have a sixteen-character character set to work with.
  127. I woulnd&apos;t have even a full alphabet, but I&apos;d have eight-character error strings to work with.
  128. If I use five-bit characters, I have a thirty-two character character set to work with, which would give me every capital <abbr title="American Standard Code for Information Interchange">ASCII</abbr> letter to work with and either some digits or some punctuation.
  129. I&apos;d have six-character strings with two flag bits.
  130. With six-bit characters, I&apos;d have five-character strings, again with two flag bits.
  131. I&apos;d also have a sixty-four character character set to work with.
  132. The obvious choice in character sets would be the base sixty-four character set specified by <a href="https://tools.ietf.org./html/rfc4648#section-4"><abbr title="Request for Comments">RFC</abbr> 4648</a>.
  133. That would give me all fifty-two <abbr title="American Standard Code for Information Interchange">ASCII</abbr> letters, all ten digits, slashes, and plus signs.
  134. That&apos;s about the upper limit on character set sizes.
  135. Adding another bit would provide a one hundred twenty-eight character character set, but there&apos;s not enough printable <abbr title="American Standard Code for Information Interchange">ASCII</abbr> characters to make use of the full space.
  136. The available space is far too limited to include Unicode characters.
  137. Five-bit character, six-character codes and six-bit character, five-character codes seem like the best options.
  138. Both options provide two extra bits to use as flags, so why not use both? The first flag can be used to determine if the exception was thrown from a function/method or from user code.
  139. The second flag can be used to determine if the numeric error code represents a string using a five-bit character character set or a six-bit character character string.
  140. </p>
  141. <p>
  142. I set about building the functions that implement what I described above, but I found that they don&apos;t work when I use the &quot;function/method&quot; flag, my exception code strings can no longer be translated back from integers.
  143. Instead, they end up translated to new strings.
  144. It took me forever to track down the bug.
  145. For some reason, I thought that signed integers behave in a very strange way bitwise when dealing with negative numbers.
  146. This isn&apos;t the case at all, and they actually behave <a href="http://kias.dyndns.org./comath/13.html">very consistently</a> and in exactly the way that I thought that they should be implemented.
  147. I have no idea where I got the screwy format from that I thought that signed integers use.
  148. In any case, fixing this is going to be a pain.
  149. <abbr title="PHP: Hypertext Preprocessor">PHP</abbr> doesn&apos;t have a concept of unsigned integers, which would make stuffing values into integers easy.
  150. Likewise, <abbr title="PHP: Hypertext Preprocessor">PHP</abbr>s signed integers vary in length depending on platform.
  151. I can&apos;t depend on them to be of a particular size.
  152. I&apos;m probably going to have to work arround this with some funky conditional padding.
  153. If positive, I need to pad with zeros, if negative, I need to pad with ones.
  154. The padding will likely have to be done with a bitmask that is obtained by taking -1 and removing the least-significant thirty-one bits.
  155. It seems like this is going to be a headache.
  156. </p>
  157. <p>
  158. Some people are trying to build a community at <a href="ircs://kitsune6uv4dtdve.onion:6697/%23Lisp">#Lisp on Volatile</a>, so I&apos;ve been hanging out there to provide another nick for the list and act as a greeter.
  159. I&apos;ve been talking about my attempts to store strings in integers there because it&apos;s programming-related, so it&apos;s somewhat-tangent to Lisp.
  160. There&apos;s not enough people there to have regular discussions on Lisp yet, so I figured it might get people talking.
  161. I mentioned the unreliability of integer lengths, which made devnull question if I was even speaking about Lisp, as <abbr title="PHP: Hypertext Preprocessor">PHP</abbr> is probably one of the few languages that even has this issue; it&apos;s unlikely that Lisp does.
  162. Upon explaining that I was using <abbr title="PHP: Hypertext Preprocessor">PHP</abbr> and not Lisp, z said that the solution was to switch to Lisp.
  163. I brought up my need for real name spaces and asked if Lisp had them, so he gave me a link to what I think is a <a href="https://github.com/guicho271828/lisp-namespace">Lisp name space module</a>.
  164. This tells me that Lisp doesn&apos;t have name spaces in the core language, but this module might fix that.
  165. I don&apos;t understand the module though, so I&apos;m not sure if it provides what I need.
  166. I think I&apos;d need to learn Lisp before I can understand the module enough to know if it fits my needs.
  167. I suppose I&apos;ll add learning Lisp to my to do list, though I really don&apos;t have time to work on that right now.
  168. It&apos;ll have to wait.
  169. </p>
  170. <hr/>
  171. <p>
  172. Copyright © 2016 Alex Yst;
  173. You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
  174. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  175. My address is in the source comments near the top of this document.
  176. This license also applies to embedded content such as images.
  177. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  178. </p>
  179. <p>
  180. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  181. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F03-March%2F29.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F03-March%2F29.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  182. </p>
  183. </body>
  184. </html>