| Subject: | fix and linkify misleading MIDI::Events |
As subject
| Subject: | opus.patch |
--- Opus.pm.orig 2013-01-31 14:19:47.000000000 +0000
+++ Opus.pm 2015-10-12 15:05:06.000000000 +0000
@@ -64,8 +64,8 @@
If you specify either C<from_file> or C<from_handle>, you probably
don't want to specify any of the other options -- altho you may well
want to specify options that'll get passed down to the decoder in
-MIDI::Events, such as 'include' => ['sysex_f0', 'sysex_f7'], just for
-example.
+L<MIDI::Event>, such as C<'include' => ['sysex_f0', 'sysex_f7']>, just
+for example.
Finally, the option C<no_parse> can be used in conjuction with either
C<from_file> or C<from_handle>, and, if true, will block MTrk tracks'
@@ -74,7 +74,7 @@
are just moving tracks around across files (or just counting them in
files, as in the code in the Synopsis, above), without having to deal
with any of the events in them. (Actually, this option is implemented
-in code in MIDI::Track, but in a routine there that I've left
+in code in L<MIDI::Track>, but in a routine there that I've left
undocumented, as you should access it only thru here.)
=cut