mkrf 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (186) hide show
  1. data/CHANGELOG +2 -0
  2. data/MIT-LICENSE +7 -0
  3. data/README +54 -0
  4. data/Rakefile +107 -0
  5. data/lib/mkrf.rb +4 -0
  6. data/lib/mkrf/availability.rb +219 -0
  7. data/lib/mkrf/generator.rb +146 -0
  8. data/test/abstract_unit.rb +4 -0
  9. data/test/fixtures/down_a_directory/header_down_a_directory.h +1 -0
  10. data/test/fixtures/stdmkrf.h +1 -0
  11. data/test/sample_files/libtrivial/Rakefile +31 -0
  12. data/test/sample_files/libtrivial/extconf.rb +3 -0
  13. data/test/sample_files/libtrivial/lib/libtrivial.c +5 -0
  14. data/test/sample_files/libtrivial/lib/libtrivial.o +0 -0
  15. data/test/sample_files/libtrivial/libtrivial_so.bundle +0 -0
  16. data/test/sample_files/libtrivial/mkrf.log +1 -0
  17. data/test/sample_files/libxml-ruby-0.3.8/CHANGELOG +74 -0
  18. data/test/sample_files/libxml-ruby-0.3.8/LICENSE +22 -0
  19. data/test/sample_files/libxml-ruby-0.3.8/README +144 -0
  20. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/cbg.c +76 -0
  21. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/extconf.rb +49 -0
  22. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/libxml.c +86 -0
  23. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/libxml.h +82 -0
  24. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/libxml.rb +107 -0
  25. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/mkrf.log +1 -0
  26. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/old_extconf.rb +95 -0
  27. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_attr.c +372 -0
  28. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_attr.h +21 -0
  29. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_attribute.c +224 -0
  30. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_attribute.h +21 -0
  31. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_document.c +1159 -0
  32. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_document.h +27 -0
  33. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_dtd.c +168 -0
  34. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_dtd.h +17 -0
  35. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_input_cbg.c +167 -0
  36. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_input_cbg.h +21 -0
  37. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_node.c +2139 -0
  38. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_node.h +28 -0
  39. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_node_set.c +248 -0
  40. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_node_set.h +26 -0
  41. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_ns.c +153 -0
  42. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_ns.h +21 -0
  43. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_parser.c +1417 -0
  44. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_parser.h +31 -0
  45. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_parser_context.c +715 -0
  46. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_parser_context.h +22 -0
  47. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_sax_parser.c +426 -0
  48. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_sax_parser.h +52 -0
  49. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_schema.c +142 -0
  50. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_schema.h +16 -0
  51. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_tree.c +43 -0
  52. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_tree.h +12 -0
  53. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_xinclude.c +20 -0
  54. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_xinclude.h +13 -0
  55. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_xpath.c +363 -0
  56. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_xpath.h +24 -0
  57. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_xpath_context.c +125 -0
  58. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_xpath_context.h +24 -0
  59. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_xpointer.c +100 -0
  60. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_xpointer.h +27 -0
  61. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_xpointer_context.c +21 -0
  62. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/ruby_xml_xpointer_context.h +18 -0
  63. data/test/sample_files/libxml-ruby-0.3.8/ext/xml/sax_parser_callbacks.inc +202 -0
  64. data/test/sample_files/syck-0.55/CHANGELOG +186 -0
  65. data/test/sample_files/syck-0.55/COPYING +54 -0
  66. data/test/sample_files/syck-0.55/Makefile +582 -0
  67. data/test/sample_files/syck-0.55/Makefile.am +5 -0
  68. data/test/sample_files/syck-0.55/Makefile.in +582 -0
  69. data/test/sample_files/syck-0.55/README +105 -0
  70. data/test/sample_files/syck-0.55/README.BYTECODE +484 -0
  71. data/test/sample_files/syck-0.55/README.EXT +444 -0
  72. data/test/sample_files/syck-0.55/RELEASE +123 -0
  73. data/test/sample_files/syck-0.55/TODO +25 -0
  74. data/test/sample_files/syck-0.55/aclocal.m4 +883 -0
  75. data/test/sample_files/syck-0.55/bootstrap +7 -0
  76. data/test/sample_files/syck-0.55/config.h +79 -0
  77. data/test/sample_files/syck-0.55/config.h.in +78 -0
  78. data/test/sample_files/syck-0.55/config.status +1197 -0
  79. data/test/sample_files/syck-0.55/config/README +14 -0
  80. data/test/sample_files/syck-0.55/config/depcomp +529 -0
  81. data/test/sample_files/syck-0.55/config/install-sh +323 -0
  82. data/test/sample_files/syck-0.55/config/missing +357 -0
  83. data/test/sample_files/syck-0.55/configure +6728 -0
  84. data/test/sample_files/syck-0.55/configure.in +36 -0
  85. data/test/sample_files/syck-0.55/ext/ruby/CHANGELOG +303 -0
  86. data/test/sample_files/syck-0.55/ext/ruby/README +400 -0
  87. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/MANIFEST +1 -0
  88. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/bytecode.c +1170 -0
  89. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/emitter.c +1224 -0
  90. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/extconf.rb +10 -0
  91. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/gram.c +1894 -0
  92. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/gram.h +79 -0
  93. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/handler.c +174 -0
  94. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/implicit.c +2989 -0
  95. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/mkrf.log +1 -0
  96. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/node.c +407 -0
  97. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/rubyext.c +2385 -0
  98. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/syck.c +504 -0
  99. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/syck.h +458 -0
  100. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/token.c +2707 -0
  101. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/yaml2byte.c +250 -0
  102. data/test/sample_files/syck-0.55/ext/ruby/ext/syck/yamlbyte.h +170 -0
  103. data/test/sample_files/syck-0.55/ext/ruby/install.rb +1022 -0
  104. data/test/sample_files/syck-0.55/ext/ruby/lib/okay.rb +161 -0
  105. data/test/sample_files/syck-0.55/ext/ruby/lib/okay/news.rb +69 -0
  106. data/test/sample_files/syck-0.55/ext/ruby/lib/okay/rpc.rb +434 -0
  107. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml.rb +436 -0
  108. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/baseemitter.rb +247 -0
  109. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/basenode.rb +216 -0
  110. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/compat.rb +26 -0
  111. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/constants.rb +45 -0
  112. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/dbm.rb +111 -0
  113. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/emitter.rb +107 -0
  114. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/encoding.rb +33 -0
  115. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/error.rb +34 -0
  116. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/rubytypes.rb +438 -0
  117. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/store.rb +29 -0
  118. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/stream.rb +40 -0
  119. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/stringio.rb +83 -0
  120. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/syck.rb +19 -0
  121. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/tag.rb +86 -0
  122. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/types.rb +188 -0
  123. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/yamlnode.rb +54 -0
  124. data/test/sample_files/syck-0.55/ext/ruby/lib/yaml/ypath.rb +52 -0
  125. data/test/sample_files/syck-0.55/ext/ruby/lib/yod.rb +1168 -0
  126. data/test/sample_files/syck-0.55/ext/ruby/samples/okayNews-modules.rb +27 -0
  127. data/test/sample_files/syck-0.55/ext/ruby/samples/okayNews-sample.rb +336 -0
  128. data/test/sample_files/syck-0.55/ext/ruby/samples/okayNews-validate.rb +341 -0
  129. data/test/sample_files/syck-0.55/ext/ruby/samples/okayRpc-client.rb +51 -0
  130. data/test/sample_files/syck-0.55/ext/ruby/samples/okayRpc-server.rb +85 -0
  131. data/test/sample_files/syck-0.55/ext/ruby/samples/yaml-sortHashKeys.rb +128 -0
  132. data/test/sample_files/syck-0.55/ext/ruby/tests/basic.rb +1653 -0
  133. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsAnchorAlias.yml +51 -0
  134. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsBasicTests.yml +282 -0
  135. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsBlockMapping.yml +78 -0
  136. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsBlockSequence.yml +0 -0
  137. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsDocumentSeparator.yml +102 -0
  138. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsErrorTests.yml +23 -0
  139. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsFlowCollections.yml +73 -0
  140. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsFoldedScalars.yml +215 -0
  141. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsMapInSeq.yml +0 -0
  142. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsNullsAndEmpties.yml +66 -0
  143. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsRubyTests.yml +182 -0
  144. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsSpecificationExamples.yml +2699 -0
  145. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsTypeTransfers.yml +265 -0
  146. data/test/sample_files/syck-0.55/ext/ruby/yts/YtsYpath.yml +221 -0
  147. data/test/sample_files/syck-0.55/ext/ruby/yts/cookbook.rb +159 -0
  148. data/test/sample_files/syck-0.55/ext/ruby/yts/index.yml +10 -0
  149. data/test/sample_files/syck-0.55/ext/ruby/yts/yts.rb +193 -0
  150. data/test/sample_files/syck-0.55/lib/Makefile +497 -0
  151. data/test/sample_files/syck-0.55/lib/Makefile.am +27 -0
  152. data/test/sample_files/syck-0.55/lib/Makefile.in +497 -0
  153. data/test/sample_files/syck-0.55/lib/bytecode.c +1170 -0
  154. data/test/sample_files/syck-0.55/lib/bytecode.re +525 -0
  155. data/test/sample_files/syck-0.55/lib/emitter.c +1224 -0
  156. data/test/sample_files/syck-0.55/lib/gram.c +1894 -0
  157. data/test/sample_files/syck-0.55/lib/gram.h +79 -0
  158. data/test/sample_files/syck-0.55/lib/gram.output +2005 -0
  159. data/test/sample_files/syck-0.55/lib/gram.y +481 -0
  160. data/test/sample_files/syck-0.55/lib/handler.c +174 -0
  161. data/test/sample_files/syck-0.55/lib/implicit.c +2989 -0
  162. data/test/sample_files/syck-0.55/lib/implicit.re +206 -0
  163. data/test/sample_files/syck-0.55/lib/node.c +407 -0
  164. data/test/sample_files/syck-0.55/lib/syck.c +504 -0
  165. data/test/sample_files/syck-0.55/lib/syck.h +458 -0
  166. data/test/sample_files/syck-0.55/lib/syck_st.c +577 -0
  167. data/test/sample_files/syck-0.55/lib/syck_st.h +46 -0
  168. data/test/sample_files/syck-0.55/lib/token.c +2707 -0
  169. data/test/sample_files/syck-0.55/lib/token.re +1139 -0
  170. data/test/sample_files/syck-0.55/lib/yaml2byte.c +250 -0
  171. data/test/sample_files/syck-0.55/lib/yamlbyte.h +170 -0
  172. data/test/sample_files/syck-0.55/stamp-h1 +1 -0
  173. data/test/sample_files/syck-0.55/tests/Basic.c +141 -0
  174. data/test/sample_files/syck-0.55/tests/CuTest.c +294 -0
  175. data/test/sample_files/syck-0.55/tests/CuTest.h +84 -0
  176. data/test/sample_files/syck-0.55/tests/Emit.c +87 -0
  177. data/test/sample_files/syck-0.55/tests/Makefile +480 -0
  178. data/test/sample_files/syck-0.55/tests/Makefile.am +13 -0
  179. data/test/sample_files/syck-0.55/tests/Makefile.in +480 -0
  180. data/test/sample_files/syck-0.55/tests/Parse.c +208 -0
  181. data/test/sample_files/syck-0.55/tests/YTS.c +2310 -0
  182. data/test/sample_files/syck-0.55/tests/YTS.c.erb +326 -0
  183. data/test/sample_files/syck-0.55/tests/YTS.c.rb +44 -0
  184. data/test/test_availability.rb +68 -0
  185. data/test/test_generator.rb +74 -0
  186. metadata +252 -0
@@ -0,0 +1,27 @@
1
+
2
+ require 'okay/news'
3
+
4
+ p YAML::load( DATA )
5
+
6
+ __END__
7
+ --- %YAML:1.0 !okay/news
8
+ title: whytheluckystiff.net
9
+ link: http://www.whytheluckystiff.net/
10
+ description: Home remedies for braindeath.
11
+ updatePeriod: 01:00:00
12
+ items:
13
+ - !okay/news/item
14
+ pubTime: 2002-10-23T09:03:40.00-06:00
15
+ link: http://whytheluckystiff.net/arch/2002/10/23#1035385420
16
+ dc;test: 1
17
+ description: >
18
+ Considering the
19
+ "discussion"="http://philringnalda.com/archives/002359.php"
20
+
21
+ - !okay/news/item
22
+ pubTime: 2002-10-22T23:46:57.00-06:00
23
+ link: http://whytheluckystiff.net/arch/2002/10/22#1035352017
24
+ dc;test: 1
25
+ description: >
26
+ Last night I hung out at this hotel with my relatives, all
27
+ in town to see
@@ -0,0 +1,336 @@
1
+ require 'okay/news'
2
+
3
+ # Wrapping strings for display
4
+ class String
5
+ def wordwrap( len )
6
+ gsub( /\n\s*/, "\n\n" ).gsub( /.{#{len},}?\s+/, "\\0\n" )
7
+ end
8
+ end
9
+
10
+ news = YAML::load( DATA )
11
+ news.items.each { |item|
12
+ puts "-- #{ news.title } @ #{ item.pubTime } --"
13
+ puts item.description.wordwrap( 70 ).gsub!( /^/, ' ' )
14
+ puts
15
+ }
16
+
17
+ __END__
18
+ --- %YAML:1.0 !okay/news
19
+ title: whytheluckystiff.net
20
+ link: http://www.whytheluckystiff.net/
21
+ description: Home remedies for braindeath.
22
+ updatePeriod: 00:60.00
23
+ items:
24
+ - !okay/news/item
25
+ pubTime: 2002-10-23T09:03:40.00-06:00
26
+ link: http://whytheluckystiff.net/arch/2002/10/23#1035385420
27
+ description: >
28
+ Considering the
29
+ "discussion"="http://philringnalda.com/archives/002359.php"
30
+ around the Web about saving RSS bandwidth, I checked the
31
+ size of my RSS feed: 33k. And my YAML feed: 15k. A big
32
+ part of that is my content included twice for the
33
+ "content:encoded"="http://web.resource.org/rss/1.0/modules/content/"
34
+ tag. Which brings up another valid point in favor of YAML
35
+ feeds. **YAML doesn't have entity-encoding issues.** XML
36
+ users: can you imagine?
37
+
38
+ - !okay/news/item
39
+ pubTime: 2002-10-22T23:46:57.00-06:00
40
+ link: http://whytheluckystiff.net/arch/2002/10/22#1035352017
41
+ description: >
42
+ Last night I hung out at this hotel with my relatives, all
43
+ in town to see
44
+ "Dot"="http://www.whytheluckystiff.net/arch/2002/10/20#1035131109".
45
+ I haven't wanted to post here on my site all the events
46
+ concerning her death, even though I
47
+ "abandoned"="http://www.whytheluckystiff.net/arch/2002/10/07#1034018848"
48
+ my paper journal to write on this site. I think I need to
49
+ flag some entries as private. Because it's too wierd
50
+ having a site where one minute I'm jabbering about YAML
51
+ ideas and the next I'm going into the details of ovarian
52
+ cancer or the rifts in my family life. Sure, I want both
53
+ documented. But I think I can tell what entries are meant
54
+ for you and what is meant for me.
55
+
56
+ I'm going to write anyway, though. Under her closed eyes,
57
+ she went away on Sunday night at 8:12 PM. She did go
58
+ naturally, as we all wished. You know, I've never had a
59
+ life like I have right now. Feeling her with me now.
60
+ Believing that she is somewhere now. Why do I insist on
61
+ thinking that? They all think she's been ushered off a
62
+ plane and onto some tropical beach, a part of some Carnival
63
+ cruise that you get for free after you die. Run by the
64
+ Carnival people who died and their heaven is continuing
65
+ their employment. (Why am I telling heaven jokes?)
66
+
67
+ I feel love, so I think about her. Her death was a sunset.
68
+ As the sun is buried, it still casts the colors upon the
69
+ world for a while longer. I see those colors in my life
70
+ now. It's either her literal dispersement into the air or
71
+ she is simply so joyful now that I can feel her happiness
72
+ from my vantage point. Can I just tell you: it's so
73
+ incredible to know someone who had no agenda, who never got
74
+ offended, who wielded such power but never used it against
75
+ anyone?
76
+
77
+ So, the hotel. We went downstairs and lounged in the
78
+ jacuzzi. Talked about work, baseball, Dot and Ray. We did
79
+ some dives into the pool.
80
+
81
+ One guy walked in with his pecs and abs with his chick and
82
+ messed around in the pool. Dancing around with each other
83
+ and playing naughty, splashy pool games with each other.
84
+ Suddenly they were in the jacuzzi with all of us. It was
85
+ whack. It was _The Bachelor_. I think I even said, "Hey,
86
+ are you *The Bachelor*?" He went and told on us for having
87
+ too many people in the pool and *especially* in the
88
+ jacuzzi. My aunt and uncle had to move hotels.
89
+
90
+ And that's when I started to question the beauty of life
91
+ again.
92
+
93
+ - !okay/news/item
94
+ pubTime: 2002-10-21T15:34:31.00-06:00
95
+ link: http://whytheluckystiff.net/arch/2002/10/21#1035236071
96
+ description: >
97
+ Today I've decided to rewrite the parser backend for
98
+ yaml.rb. The new parser will be called **Pill** and will
99
+ also become the secret behind
100
+ "reStructuredText"="http://docutils.sf.net/rst.html" for
101
+ Ruby. The reST team has put some excellent effort into
102
+ documenting and producing code for their project. YAML and
103
+ reST share so much in common that I thought I could save a
104
+ lot of time by abstracting the parser so that it can handle
105
+ both.
106
+
107
+ To give you an idea of what I mean, just look at the
108
+ following Ruby code. To create a parser, you merely extend
109
+ the Pill class and define the meaning of your tokens:
110
+
111
+ = class YamlParser < Pill
112
+ = # Define YAML's literal block
113
+ = def_token :block, :literal,
114
+ = [ '|' ], [ :entry ]
115
+ = # Define mapping indicator
116
+ = def_token :indicator, :mapping,
117
+ = [ ':', :space ]
118
+ = end
119
+
120
+ This is prototype code. Hopefully it gives the picture
121
+ though. I define the specific syntax symbols and the
122
+ parser sends them to event handlers which can construct
123
+ native datatypes (YAML) or markup (reST).
124
+
125
+ - !okay/news/item
126
+ pubTime: 2002-10-21T13:25:25.00-06:00
127
+ link: http://whytheluckystiff.net/arch/2002/10/21#1035228325
128
+ description: >
129
+ Okay, so I just found an
130
+ "FAQ"="http://otakuworld.com/games/saturn/vs_moves.htm" for
131
+ **Vampire Saviour: World of Darkness**, the game I "raved
132
+ about"="http://advogato.org/article/562.html" on Advogato.
133
+ The article was likely misplaced. Thinking about it now I
134
+ can't imagine why I posted it there, but I thought it would
135
+ be fun. Probably was fun. Keep in mind that this is an
136
+ old game now and since I don't say that in the article it
137
+ probably sounds like I'm plugging some new, hot commercial
138
+ game. No way. This game is dead. And time for a
139
+ resurrection!
140
+
141
+ It turns out that the reason I can't find any information
142
+ about **Vampire Saviour: World of Darkness** is because the
143
+ game isn't really even called that. Yes, that's the name
144
+ on the arcade machine. I wasn't paying attention to the
145
+ title screen, though, which probably said **The Lord of
146
+ Vampire**. At any rate, I didn't see a single vampire in
147
+ this whole game. Not to mention that it was a bright and
148
+ colorful game (not a World of Darkness as one might
149
+ suppose).
150
+
151
+ With all the love that I have in my bosom for this fine
152
+ Capcom production, I feel that I must rename it for use in
153
+ my private spheres of influence. In my associations with
154
+ humanity, I will now refer to this game as **The Organism
155
+ of Life-giving Eternity**. So it is. So it is.
156
+
157
+ - !okay/news/item
158
+ pubTime: 2002-10-20T10:25:09.00-06:00
159
+ link: http://whytheluckystiff.net/arch/2002/10/20#1035131109
160
+ description: >
161
+ My grandmother has slipped into a coma and will likely close
162
+ her life in the next few days. We've actually had her much
163
+ longer than we were supposed to. It's been a wonderful
164
+ time to be with her.
165
+
166
+ Her name is Dot and I think of her often. She's one of
167
+ those people in my family tree that I really hope a lot of
168
+ genes seep down from. She spent her whole life fully
169
+ devoted to her husband. Their life was golf, Hawaii,
170
+ gambling, their children. Her husband now has Alzheimer's
171
+ and she has taught us that Alzheimer's isn't a frightening
172
+ or sad disease. She helps us see how cute he is and how he
173
+ still does remember who we are. Maybe he doesn't recognize
174
+ our faces, but he recognizes something. And so it's up to
175
+ us to recognize him back.
176
+
177
+ Dot makes me laugh everytime I am with her. One of my
178
+ favorites was when she looked up at my mom and said, "I was
179
+ in love with two black men." She can say whatever she
180
+ wants these days and she does. She thinks her doctors are
181
+ sexy. She watches lots of baseball, a life-long Dodger's
182
+ fan, but also general fan of the game.
183
+
184
+ I should stop writing now. I just can't think about it all
185
+ today. Approaching death has been so hard for her. I just
186
+ wish her death could be as natural as the rest of her life
187
+ has been.
188
+
189
+ - !okay/news/item
190
+ pubTime: 2002-10-19T11:02:53.00-06:00
191
+ link: http://whytheluckystiff.net/arch/2002/10/19#1035046973
192
+ description: >
193
+ Watching the "RSS 1.0/2.0
194
+ logomachy"="http://diveintomark.org/archives/2002/10/18.html#take_up_knitting"
195
+ is evocative in light of a new "YAML
196
+ equivalent"="http://whytheluckystiff.net/why.yml". The
197
+ struggle in the YAML world will be trying to steer people
198
+ away from interleaving content. (The tags with namespaces
199
+ you see mixed in with the RSS tags.) The struggle is: what
200
+ is our answer? See the collection of links at the end of
201
+ "Mark's"="http://diveintomark.org/" posting, along with the
202
+ "XSS
203
+ Draft"="http://www.mplode.com/tima/archives/000126.html".
204
+
205
+ - !okay/news/item
206
+ pubTime: 2002-10-19T10:46:36.00-06:00
207
+ link: http://whytheluckystiff.net/arch/2002/10/19#1035045996
208
+ description: >
209
+ About distribution in the Ruby kingdom. I think
210
+ "CPAN"="http://search.cpan.org/" has put a bit of undue
211
+ pressure on us. I personally use CPAN for documentation
212
+ and for comparing modules before downloading them. I don't
213
+ use CPAN to install modules. I use the ports collection or
214
+ (on Linux) the packaging system.
215
+
216
+ Ruby has "RAA"="http://www.ruby-lang.org/en/raa.html". RAA
217
+ is less than what we need. RAA has some great stuff. You
218
+ can access it through web services. I just wish it had a
219
+ more comprehensive search and extensive documentation for
220
+ each module. And package mirrors. Make sure we don't
221
+ loose our libraries.
222
+
223
+ Two RAA replacements are in progress, both of which I took
224
+ a close look at today.
225
+
226
+ # "rpkg"="http://www.allruby.com/rpkg/" is great. It's a
227
+ Debian-like packaging system for Ruby modules. I don't
228
+ know exactly how they solve the mirroring issues and
229
+ there's no accessibility to module docs and definitions
230
+ online, but it's got some neat ideas.
231
+ # "rubynet"="http://www.rubynet.org/" is a precocious
232
+ project to do about anything you could want to do with Ruby
233
+ packaging. I'm still trying to decide if it's overkill.
234
+ Again, plenty of ideas to ease installation but no hints of
235
+ making each package's docs available.
236
+
237
+ I don't think Ruby users have a large problem installing
238
+ modules. Most modules are quite straightforward. The
239
+ bigger issue is organization and documentation. Are we the
240
+ only group who hasn't standardized on a doc format!?
241
+
242
+ - !okay/news/item
243
+ pubTime: 2002-10-19T01:25:46.00-06:00
244
+ link: http://whytheluckystiff.net/arch/2002/10/19#1035012346
245
+ description: >
246
+ I am aghast! YAML.rb 0.44 is now in the FreeBSD ports
247
+ collection! Sitting right there in
248
+ /usr/ports/devel/ruby-yaml! It installs perfectly.
249
+
250
+ There are two amazing things about this:
251
+
252
+ # Stanislav Grozev did this without any provocation from
253
+ me.
254
+ # I've actually seen one of my software projects through to
255
+ see some sort of general distribution and acceptance!
256
+
257
+ Seriously, what a kick! The ports collection is like the
258
+ Hall of Fame for me. I cvsup fresh ports at least weekly
259
+ and I have for the last several years. I probably
260
+ shouldn't be making such a big deal out of it, but it's so
261
+ rewarding to see that someone appreciates this library
262
+ enough to help step it along for distribution. *Thank you,
263
+ Stanislav!*
264
+
265
+ - !okay/news/item
266
+ pubTime: 2002-10-18T13:50:57.00-06:00
267
+ link: http://whytheluckystiff.net/arch/2002/10/18#1034970657
268
+ description: >
269
+ I know there's some incredible uses for YAML and
270
+ documentation, but it's difficult to grasp exactly what
271
+ that is. Stefan Schmiedl posted an idea to the Yaml-core
272
+ list last month:
273
+
274
+ > What I had in mind was a "layered" wiki approach, where
275
+ you would organize YAML-documents to create a page. You
276
+ would edit the "nodes" of the page via usual wiki approach
277
+ or modify the sequence collecting the docs. At the end of
278
+ the day you'd have a large collection of YAML-docs and a
279
+ second collection of "organizers" collating them into
280
+ pages.
281
+
282
+ The time is soon coming where this will be available here
283
+ on this site. I'm thinking of something similiar to Wiki.
284
+ The difference would be that the content would be updated
285
+ to YAML documents on the server in Yod format. The
286
+ documents could then be exported to HTML, man pages, CHM,
287
+ PDF. It would be Wiki, but with a real end toward polished
288
+ documentation.
289
+
290
+ I want to store organized text on this site in such a way
291
+ that it can be removed from the site, distributable, and
292
+ yet very easy to edit.
293
+
294
+ - !okay/news/item
295
+ pubTime: 2002-10-18T10:01:49.00-06:00
296
+ link: http://whytheluckystiff.net/arch/2002/10/18#1034956909
297
+ description: >
298
+ **Coldplay: A Rush of Blood to the Head**
299
+
300
+ Despite what the music press might say, I feel obliged to
301
+ like whatever music I please to like. And yet, when I read
302
+ something about an album, I let it easily influence my
303
+ listening. For a few weeks at least. If some poor review
304
+ keeps me from hearing an album or I can't make it through
305
+ the album a few times, then likely I've missed the chance
306
+ to hear the music as the artist intended it.
307
+
308
+ I don't know why I gave **A Rush of Blood to the Head** a
309
+ chance really. I remember being unimpressed with
310
+ Coldplay's first effort. Not to mention that the public's
311
+ admiration of the band was rather discouraging. But these
312
+ days I find myself opening back up to **Weezer**, **Ben
313
+ Kweller**, **Supergrass**. Perhaps I have a diluted
314
+ catalog, but I really enjoy the songs. What can I say?
315
+
316
+ The song "Clocks" struck me in a peculiar way. The song
317
+ simply turned my opinion. I actually heard his voice as he
318
+ intended. I fancied his use of repetition. I went back
319
+ and listened again. This song had a very warm emotion
320
+ attached. The disc continued to play and that's when I
321
+ realized that all of Coldplay's songs have that same
322
+ emotion spun throughout.
323
+
324
+ Perhaps that's a strike against the band. Their feeling
325
+ fluctuates between songs, but they don't ever get
326
+ terrifically angry. Nor do they pity themselves much. If
327
+ they don't explore all of those avenues of thought, how can
328
+ they very well be songwriters at all? Coldplay simply
329
+ shines like a dazzle of light across a country lake.
330
+ Constantly and slightly beautiful.
331
+
332
+ I'm not the sort of person who can bore of natural beauty.
333
+ I don't imagine many people can look at a sunset and
334
+ discard it thanks to the monotony of sunsets each day. It
335
+ turns out that Coldplay makes beautiful music, which fills
336
+ a definite void in my collection.
@@ -0,0 +1,341 @@
1
+ require 'okay/news'
2
+
3
+ # Wrapping strings for display
4
+ class String
5
+ def wordwrap( len )
6
+ gsub( /\n\s*/, "\n\n" ).gsub( /.{#{len},}?\s+/, "\\0\n" )
7
+ end
8
+ end
9
+
10
+ news = YAML::parse( DATA )
11
+ if Okay.validate_node( news )
12
+ puts "** !okay/news validated **"
13
+ news = news.transform
14
+ news.items.each { |item|
15
+ puts "-- #{ news.title } @ #{ item.pubTime } --"
16
+ puts item.description.wordwrap( 70 ).gsub!( /^/, ' ' )
17
+ puts
18
+ }
19
+ end
20
+
21
+
22
+ __END__
23
+ --- %YAML:1.0 !okay/news
24
+ title: whytheluckystiff.net
25
+ link: http://www.whytheluckystiff.net/
26
+ description: Home remedies for braindeath.
27
+ updatePeriod: 00:60.00
28
+ items:
29
+ - !okay/news/item
30
+ pubTime: 2002-10-23T09:03:40.00-06:00
31
+ link: http://whytheluckystiff.net/arch/2002/10/23#1035385420
32
+ description: >
33
+ Considering the
34
+ "discussion"="http://philringnalda.com/archives/002359.php"
35
+ around the Web about saving RSS bandwidth, I checked the
36
+ size of my RSS feed: 33k. And my YAML feed: 15k. A big
37
+ part of that is my content included twice for the
38
+ "content:encoded"="http://web.resource.org/rss/1.0/modules/content/"
39
+ tag. Which brings up another valid point in favor of YAML
40
+ feeds. **YAML doesn't have entity-encoding issues.** XML
41
+ users: can you imagine?
42
+
43
+ - !okay/news/item
44
+ pubTime: 2002-10-22T23:46:57.00-06:00
45
+ link: http://whytheluckystiff.net/arch/2002/10/22#1035352017
46
+ description: >
47
+ Last night I hung out at this hotel with my relatives, all
48
+ in town to see
49
+ "Dot"="http://www.whytheluckystiff.net/arch/2002/10/20#1035131109".
50
+ I haven't wanted to post here on my site all the events
51
+ concerning her death, even though I
52
+ "abandoned"="http://www.whytheluckystiff.net/arch/2002/10/07#1034018848"
53
+ my paper journal to write on this site. I think I need to
54
+ flag some entries as private. Because it's too wierd
55
+ having a site where one minute I'm jabbering about YAML
56
+ ideas and the next I'm going into the details of ovarian
57
+ cancer or the rifts in my family life. Sure, I want both
58
+ documented. But I think I can tell what entries are meant
59
+ for you and what is meant for me.
60
+
61
+ I'm going to write anyway, though. Under her closed eyes,
62
+ she went away on Sunday night at 8:12 PM. She did go
63
+ naturally, as we all wished. You know, I've never had a
64
+ life like I have right now. Feeling her with me now.
65
+ Believing that she is somewhere now. Why do I insist on
66
+ thinking that? They all think she's been ushered off a
67
+ plane and onto some tropical beach, a part of some Carnival
68
+ cruise that you get for free after you die. Run by the
69
+ Carnival people who died and their heaven is continuing
70
+ their employment. (Why am I telling heaven jokes?)
71
+
72
+ I feel love, so I think about her. Her death was a sunset.
73
+ As the sun is buried, it still casts the colors upon the
74
+ world for a while longer. I see those colors in my life
75
+ now. It's either her literal dispersement into the air or
76
+ she is simply so joyful now that I can feel her happiness
77
+ from my vantage point. Can I just tell you: it's so
78
+ incredible to know someone who had no agenda, who never got
79
+ offended, who wielded such power but never used it against
80
+ anyone?
81
+
82
+ So, the hotel. We went downstairs and lounged in the
83
+ jacuzzi. Talked about work, baseball, Dot and Ray. We did
84
+ some dives into the pool.
85
+
86
+ One guy walked in with his pecs and abs with his chick and
87
+ messed around in the pool. Dancing around with each other
88
+ and playing naughty, splashy pool games with each other.
89
+ Suddenly they were in the jacuzzi with all of us. It was
90
+ whack. It was _The Bachelor_. I think I even said, "Hey,
91
+ are you *The Bachelor*?" He went and told on us for having
92
+ too many people in the pool and *especially* in the
93
+ jacuzzi. My aunt and uncle had to move hotels.
94
+
95
+ And that's when I started to question the beauty of life
96
+ again.
97
+
98
+ - !okay/news/item
99
+ pubTime: 2002-10-21T15:34:31.00-06:00
100
+ link: http://whytheluckystiff.net/arch/2002/10/21#1035236071
101
+ description: >
102
+ Today I've decided to rewrite the parser backend for
103
+ yaml.rb. The new parser will be called **Pill** and will
104
+ also become the secret behind
105
+ "reStructuredText"="http://docutils.sf.net/rst.html" for
106
+ Ruby. The reST team has put some excellent effort into
107
+ documenting and producing code for their project. YAML and
108
+ reST share so much in common that I thought I could save a
109
+ lot of time by abstracting the parser so that it can handle
110
+ both.
111
+
112
+ To give you an idea of what I mean, just look at the
113
+ following Ruby code. To create a parser, you merely extend
114
+ the Pill class and define the meaning of your tokens:
115
+
116
+ = class YamlParser < Pill
117
+ = # Define YAML's literal block
118
+ = def_token :block, :literal,
119
+ = [ '|' ], [ :entry ]
120
+ = # Define mapping indicator
121
+ = def_token :indicator, :mapping,
122
+ = [ ':', :space ]
123
+ = end
124
+
125
+ This is prototype code. Hopefully it gives the picture
126
+ though. I define the specific syntax symbols and the
127
+ parser sends them to event handlers which can construct
128
+ native datatypes (YAML) or markup (reST).
129
+
130
+ - !okay/news/item
131
+ pubTime: 2002-10-21T13:25:25.00-06:00
132
+ link: http://whytheluckystiff.net/arch/2002/10/21#1035228325
133
+ description: >
134
+ Okay, so I just found an
135
+ "FAQ"="http://otakuworld.com/games/saturn/vs_moves.htm" for
136
+ **Vampire Saviour: World of Darkness**, the game I "raved
137
+ about"="http://advogato.org/article/562.html" on Advogato.
138
+ The article was likely misplaced. Thinking about it now I
139
+ can't imagine why I posted it there, but I thought it would
140
+ be fun. Probably was fun. Keep in mind that this is an
141
+ old game now and since I don't say that in the article it
142
+ probably sounds like I'm plugging some new, hot commercial
143
+ game. No way. This game is dead. And time for a
144
+ resurrection!
145
+
146
+ It turns out that the reason I can't find any information
147
+ about **Vampire Saviour: World of Darkness** is because the
148
+ game isn't really even called that. Yes, that's the name
149
+ on the arcade machine. I wasn't paying attention to the
150
+ title screen, though, which probably said **The Lord of
151
+ Vampire**. At any rate, I didn't see a single vampire in
152
+ this whole game. Not to mention that it was a bright and
153
+ colorful game (not a World of Darkness as one might
154
+ suppose).
155
+
156
+ With all the love that I have in my bosom for this fine
157
+ Capcom production, I feel that I must rename it for use in
158
+ my private spheres of influence. In my associations with
159
+ humanity, I will now refer to this game as **The Organism
160
+ of Life-giving Eternity**. So it is. So it is.
161
+
162
+ - !okay/news/item
163
+ pubTime: 2002-10-20T10:25:09.00-06:00
164
+ link: http://whytheluckystiff.net/arch/2002/10/20#1035131109
165
+ description: >
166
+ My grandmother has slipped into a coma and will likely close
167
+ her life in the next few days. We've actually had her much
168
+ longer than we were supposed to. It's been a wonderful
169
+ time to be with her.
170
+
171
+ Her name is Dot and I think of her often. She's one of
172
+ those people in my family tree that I really hope a lot of
173
+ genes seep down from. She spent her whole life fully
174
+ devoted to her husband. Their life was golf, Hawaii,
175
+ gambling, their children. Her husband now has Alzheimer's
176
+ and she has taught us that Alzheimer's isn't a frightening
177
+ or sad disease. She helps us see how cute he is and how he
178
+ still does remember who we are. Maybe he doesn't recognize
179
+ our faces, but he recognizes something. And so it's up to
180
+ us to recognize him back.
181
+
182
+ Dot makes me laugh everytime I am with her. One of my
183
+ favorites was when she looked up at my mom and said, "I was
184
+ in love with two black men." She can say whatever she
185
+ wants these days and she does. She thinks her doctors are
186
+ sexy. She watches lots of baseball, a life-long Dodger's
187
+ fan, but also general fan of the game.
188
+
189
+ I should stop writing now. I just can't think about it all
190
+ today. Approaching death has been so hard for her. I just
191
+ wish her death could be as natural as the rest of her life
192
+ has been.
193
+
194
+ - !okay/news/item
195
+ pubTime: 2002-10-19T11:02:53.00-06:00
196
+ link: http://whytheluckystiff.net/arch/2002/10/19#1035046973
197
+ description: >
198
+ Watching the "RSS 1.0/2.0
199
+ logomachy"="http://diveintomark.org/archives/2002/10/18.html#take_up_knitting"
200
+ is evocative in light of a new "YAML
201
+ equivalent"="http://whytheluckystiff.net/why.yml". The
202
+ struggle in the YAML world will be trying to steer people
203
+ away from interleaving content. (The tags with namespaces
204
+ you see mixed in with the RSS tags.) The struggle is: what
205
+ is our answer? See the collection of links at the end of
206
+ "Mark's"="http://diveintomark.org/" posting, along with the
207
+ "XSS
208
+ Draft"="http://www.mplode.com/tima/archives/000126.html".
209
+
210
+ - !okay/news/item
211
+ pubTime: 2002-10-19T10:46:36.00-06:00
212
+ link: http://whytheluckystiff.net/arch/2002/10/19#1035045996
213
+ description: >
214
+ About distribution in the Ruby kingdom. I think
215
+ "CPAN"="http://search.cpan.org/" has put a bit of undue
216
+ pressure on us. I personally use CPAN for documentation
217
+ and for comparing modules before downloading them. I don't
218
+ use CPAN to install modules. I use the ports collection or
219
+ (on Linux) the packaging system.
220
+
221
+ Ruby has "RAA"="http://www.ruby-lang.org/en/raa.html". RAA
222
+ is less than what we need. RAA has some great stuff. You
223
+ can access it through web services. I just wish it had a
224
+ more comprehensive search and extensive documentation for
225
+ each module. And package mirrors. Make sure we don't
226
+ loose our libraries.
227
+
228
+ Two RAA replacements are in progress, both of which I took
229
+ a close look at today.
230
+
231
+ # "rpkg"="http://www.allruby.com/rpkg/" is great. It's a
232
+ Debian-like packaging system for Ruby modules. I don't
233
+ know exactly how they solve the mirroring issues and
234
+ there's no accessibility to module docs and definitions
235
+ online, but it's got some neat ideas.
236
+ # "rubynet"="http://www.rubynet.org/" is a precocious
237
+ project to do about anything you could want to do with Ruby
238
+ packaging. I'm still trying to decide if it's overkill.
239
+ Again, plenty of ideas to ease installation but no hints of
240
+ making each package's docs available.
241
+
242
+ I don't think Ruby users have a large problem installing
243
+ modules. Most modules are quite straightforward. The
244
+ bigger issue is organization and documentation. Are we the
245
+ only group who hasn't standardized on a doc format!?
246
+
247
+ - !okay/news/item
248
+ pubTime: 2002-10-19T01:25:46.00-06:00
249
+ link: http://whytheluckystiff.net/arch/2002/10/19#1035012346
250
+ description: >
251
+ I am aghast! YAML.rb 0.44 is now in the FreeBSD ports
252
+ collection! Sitting right there in
253
+ /usr/ports/devel/ruby-yaml! It installs perfectly.
254
+
255
+ There are two amazing things about this:
256
+
257
+ # Stanislav Grozev did this without any provocation from
258
+ me.
259
+ # I've actually seen one of my software projects through to
260
+ see some sort of general distribution and acceptance!
261
+
262
+ Seriously, what a kick! The ports collection is like the
263
+ Hall of Fame for me. I cvsup fresh ports at least weekly
264
+ and I have for the last several years. I probably
265
+ shouldn't be making such a big deal out of it, but it's so
266
+ rewarding to see that someone appreciates this library
267
+ enough to help step it along for distribution. *Thank you,
268
+ Stanislav!*
269
+
270
+ - !okay/news/item
271
+ pubTime: 2002-10-18T13:50:57.00-06:00
272
+ link: http://whytheluckystiff.net/arch/2002/10/18#1034970657
273
+ description: >
274
+ I know there's some incredible uses for YAML and
275
+ documentation, but it's difficult to grasp exactly what
276
+ that is. Stefan Schmiedl posted an idea to the Yaml-core
277
+ list last month:
278
+
279
+ > What I had in mind was a "layered" wiki approach, where
280
+ you would organize YAML-documents to create a page. You
281
+ would edit the "nodes" of the page via usual wiki approach
282
+ or modify the sequence collecting the docs. At the end of
283
+ the day you'd have a large collection of YAML-docs and a
284
+ second collection of "organizers" collating them into
285
+ pages.
286
+
287
+ The time is soon coming where this will be available here
288
+ on this site. I'm thinking of something similiar to Wiki.
289
+ The difference would be that the content would be updated
290
+ to YAML documents on the server in Yod format. The
291
+ documents could then be exported to HTML, man pages, CHM,
292
+ PDF. It would be Wiki, but with a real end toward polished
293
+ documentation.
294
+
295
+ I want to store organized text on this site in such a way
296
+ that it can be removed from the site, distributable, and
297
+ yet very easy to edit.
298
+
299
+ - !okay/news/item
300
+ pubTime: 2002-10-18T10:01:49.00-06:00
301
+ link: http://whytheluckystiff.net/arch/2002/10/18#1034956909
302
+ description: >
303
+ **Coldplay: A Rush of Blood to the Head**
304
+
305
+ Despite what the music press might say, I feel obliged to
306
+ like whatever music I please to like. And yet, when I read
307
+ something about an album, I let it easily influence my
308
+ listening. For a few weeks at least. If some poor review
309
+ keeps me from hearing an album or I can't make it through
310
+ the album a few times, then likely I've missed the chance
311
+ to hear the music as the artist intended it.
312
+
313
+ I don't know why I gave **A Rush of Blood to the Head** a
314
+ chance really. I remember being unimpressed with
315
+ Coldplay's first effort. Not to mention that the public's
316
+ admiration of the band was rather discouraging. But these
317
+ days I find myself opening back up to **Weezer**, **Ben
318
+ Kweller**, **Supergrass**. Perhaps I have a diluted
319
+ catalog, but I really enjoy the songs. What can I say?
320
+
321
+ The song "Clocks" struck me in a peculiar way. The song
322
+ simply turned my opinion. I actually heard his voice as he
323
+ intended. I fancied his use of repetition. I went back
324
+ and listened again. This song had a very warm emotion
325
+ attached. The disc continued to play and that's when I
326
+ realized that all of Coldplay's songs have that same
327
+ emotion spun throughout.
328
+
329
+ Perhaps that's a strike against the band. Their feeling
330
+ fluctuates between songs, but they don't ever get
331
+ terrifically angry. Nor do they pity themselves much. If
332
+ they don't explore all of those avenues of thought, how can
333
+ they very well be songwriters at all? Coldplay simply
334
+ shines like a dazzle of light across a country lake.
335
+ Constantly and slightly beautiful.
336
+
337
+ I'm not the sort of person who can bore of natural beauty.
338
+ I don't imagine many people can look at a sunset and
339
+ discard it thanks to the monotony of sunsets each day. It
340
+ turns out that Coldplay makes beautiful music, which fills
341
+ a definite void in my collection.