netlinx-erb 1.0.0 → 1.1.0

data/doc/String.html

@@ -313,7 +313,7 @@
 </div>
 
     <div id="footer">
-  Generated on Fri Jan 30 17:24:15 2015 by
+  Generated on Wed Feb 25 14:28:07 2015 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.8.7.6 (ruby-2.1.3).
 </div>

data/doc/_index.html

@@ -239,7 +239,7 @@
 </div>
 
     <div id="footer">
-  Generated on Fri Jan 30 17:24:14 2015 by
+  Generated on Wed Feb 25 14:28:05 2015 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.8.7.6 (ruby-2.1.3).
 </div>

data/doc/file.README.html

@@ -68,14 +68,161 @@
 
 <p>A code generation utility for AMX NetLinx control systems.</p>
 
-<p>[todo: gem badge]</p>
+<p><a href="http://badge.fury.io/rb/netlinx-erb"><img
+src="https://badge.fury.io/rb/netlinx-erb.svg"></a> <a
+href="http://www.rubydoc.info/gems/netlinx-erb"><img
+src="http://img.shields.io/badge/docs-api-blue.svg"></a></p>
 
 <p>Syntax highlighting is included in <a
 href="https://github.com/amclain/sublime-netlinx">sublime-netlinx</a>.</p>
+
+<h2 id="label-Overview">Overview</h2>
+
+<p>Use a descriptive syntax…</p>
+
+<p><img
+src="https://github.com/amclain/netlinx-erb/blob/master/screenshots/example_erb.png"
+/></p>
+
+<p>To generate repetitive NetLinx code…</p>
+
+<p><img
+src="https://github.com/amclain/netlinx-erb/blob/master/screenshots/example_axi.png"
+/></p>
+
+<p>With netlinx-erb, configuration is separated from implementation. For
+example, touch panel button numbers and video inputs (configuration) are
+separated from the code that handles video patching when a button is
+pressed (implementation). Under this paradigm, reconfiguration can happen
+quickly as project requirements change. Since the implementation code is
+separated from these changes and code generation is automated, there is
+less chance of inducing bugs into the system when a change in configuration
+happens.</p>
+
+<p>For example, in the code above, let&#39;s say the client decides to add a
+camera to the system. All we have to do to update this file is add the
+following to the <code>video_sources</code> hash:</p>
+
+<pre class="code ruby"><code class="ruby">BTN_VID_CAMERA: { btn: 14, input: :VID_SRC_CAMERA }
+</code></pre>
+
+<p>This defines a new touch panel button constant <code>BTN_VID_CAMERA</code>,
+assigns that constant to channel number <code>14</code>, and adds a case to
+the button event handler to switch the video matrix to
+<code>VID_SRC_CAMERA</code> when the button is pressed. Since the
+implementation code for this change is auto-generated, and we know that the
+implementation code works correctly, it is unlikely that this change will
+create any bugs. There is a clear advantage to this method as the amount of
+code grows and the project becomes more complex.</p>
+
+<h3 id="label-RPC">RPC</h3>
+
+<p>A remote procedure call (RPC) mechanism is included to be able to call
+NetLinx functions through ICSLan (NetLinx Diagnostics, Telnet, etc.). To
+issue an RPC function call, <code>send_string</code> to
+<code>34500:1:0</code>. The body of the string should start with the name
+of the function, followed by a space-separated list of arguments.</p>
+
+<p>For the following function:</p>
+
+<pre class="code ruby"><code class="ruby">define_function patch_video(integer input, integer output)
+{
+    // Patch video matrix.
+}</code></pre>
+
+<p><code>patch_video 1 2</code> is the RPC string that would patch video input
+1 to output 2.</p>
+
+<h3 id="label-Backward+Compatibility">Backward Compatibility</h3>
+
+<p>The NetLinx files generated by netlinx-erb are designed to be fully
+backward compatible with traditional NetLinx project development, including
+readability and adequate whitespace. This means that any NetLinx programmer
+can take over maintenance of the project using the standard development
+tools provided by AMX and does not need to have any experience with
+netlinx-erb.</p>
+
+<p>It is important to note that <strong><em>this process is a one-way
+street</em></strong>. Once the generated files are modified by hand, the
+changes must be manually converted back to the template files or else they
+will be erased the next time the generator is run. Backward compatibility
+is designed for projects that are permanently passed to other programmers
+who are not familiar with netlinx-erb and are not able to learn it, like
+due to time constraints.</p>
+
+<h2 id="label-Issues-2C+Bugs-2C+Feature+Requests">Issues, Bugs, Feature Requests</h2>
+
+<p>Any bugs and feature requests should be reported on the GitHub issue
+tracker:</p>
+
+<p><a
+href="https://github.com/amclain/netlinx-erb/issues">github.com/amclain/netlinx-erb/issues</a></p>
+
+<p><strong>Pull requests are preferred via GitHub.</strong></p>
+
+<p>Mercurial users can use <a href="http://hg-git.github.io/">Hg-Git</a> to
+interact with GitHub repositories.</p>
+
+<h2 id="label-Installation">Installation</h2>
+
+<p>netlinx-erb is available as a Ruby gem.</p>
+<ol><li>
+<p>Install <a href="https://www.ruby-lang.org">Ruby</a> 2.1.5 or higher.</p>
+<ul><li>
+<p>Windows: Use <a
+href="http://rubyinstaller.org/downloads/">RubyInstaller</a> and make sure
+ruby/bin is in your <a
+href="http://www.computerhope.com/issues/ch000549.htm">system path</a>.</p>
+</li><li>
+<p>Linux: Use <a
+href="https://github.com/sstephenson/rbenv#basic-github-checkout">rbenv</a>.</p>
+</li><li>
+<p>Windows: Use <a
+href="http://rubyinstaller.org/downloads/">RubyInstaller</a> and make sure
+ruby/bin is in your <a
+href="http://www.computerhope.com/issues/ch000549.htm">system path</a>.</p>
+</li><li>
+<p>Linux: Use <a
+href="https://github.com/sstephenson/rbenv#basic-github-checkout">rbenv</a>.</p>
+</li></ul>
+</li><li>
+<p>Open the <a
+href="http://www.addictivetips.com/windows-tips/windows-7-elevated-command-prompt-in-context-menu/">command
+line</a> and type:</p>
+
+<p><strong><em>gem install netlinx-erb</em></strong></p>
+</li></ol>
+
+<p><em>NOTE: The NetLinx compiler executable provided by AMX, nlrc.exe, must
+be installed on your computer for this utility to work. It is included in
+the NetLinx Studio installation by default.</em></p>
+
+<p><strong>If you receive the following error when running gem
+install:</strong> <code>Unable to download data from https://rubygems.org/
+- SSL_connect returned=1</code></p>
+
+<p>Follow this guide: <a
+href="https://gist.github.com/luislavena/f064211759ee0f806c88">Workaround
+RubyGems’ SSL errors on Ruby for Windows (RubyInstaller)</a></p>
+
+<h2 id="label-Prerequisite+Knowledge">Prerequisite Knowledge</h2>
+
+<p>netlinx-erb is a complex utility and does have a learning curve. However,
+the time invested in learning this utility pays off in time saved from
+generating code that would otherwise be handwritten, and troubleshooting
+fewer bugs. Due to this, project maintenance also becomes easier.</p>
+
+<p>Basic experience with the <a href="https://www.ruby-lang.org">Ruby
+programming language</a> is required, as well as <a
+href="http://www.stuartellis.eu/articles/erb/">ERB templating</a>.</p>
+
+<h2 id="label-Getting+Started">Getting Started</h2>
+
+<h2 id="label-Code+Examples">Code Examples</h2>
 </div></div>
 
     <div id="footer">
-  Generated on Fri Jan 30 17:24:15 2015 by
+  Generated on Wed Feb 25 14:28:07 2015 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.8.7.6 (ruby-2.1.3).
 </div>

data/doc/file.license.html

@@ -61,10 +61,10 @@
 
     <iframe id="search_frame"></iframe>
 
-    <div id="content"><div id='filecontents'>The MIT License (MIT)<br/><br/>Copyright (c) 2015 Alex McLain and Joe McIlvain<br/><br/>Permission is hereby granted, free of charge, to any person obtaining a copy<br/>of this software and associated documentation files (the &quot;Software&quot;), to deal<br/>in the Software without restriction, including without limitation the rights<br/>to use, copy, modify, merge, publish, distribute, sublicense, and/or sell<br/>copies of the Software, and to permit persons to whom the Software is<br/>furnished to do so, subject to the following conditions:<br/><br/>The above copyright notice and this permission notice shall be included in<br/>all copies or substantial portions of the Software.<br/><br/>THE SOFTWARE IS PROVIDED &quot;AS IS&quot;, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR<br/>IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,<br/>FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE<br/>AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER<br/>LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,<br/>OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN<br/>THE SOFTWARE.</div></div>
+    <div id="content"><div id='filecontents'>The MIT License (MIT)<br/><br/>Copyright (c) 2014-2015 Alex McLain and Joe McIlvain<br/><br/>Permission is hereby granted, free of charge, to any person obtaining a copy<br/>of this software and associated documentation files (the &quot;Software&quot;), to deal<br/>in the Software without restriction, including without limitation the rights<br/>to use, copy, modify, merge, publish, distribute, sublicense, and/or sell<br/>copies of the Software, and to permit persons to whom the Software is<br/>furnished to do so, subject to the following conditions:<br/><br/>The above copyright notice and this permission notice shall be included in<br/>all copies or substantial portions of the Software.<br/><br/>THE SOFTWARE IS PROVIDED &quot;AS IS&quot;, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR<br/>IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,<br/>FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE<br/>AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER<br/>LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,<br/>OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN<br/>THE SOFTWARE.</div></div>
 
     <div id="footer">
-  Generated on Fri Jan 30 17:24:15 2015 by
+  Generated on Wed Feb 25 14:28:07 2015 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.8.7.6 (ruby-2.1.3).
 </div>

data/doc/index.html

@@ -68,14 +68,161 @@
 
 <p>A code generation utility for AMX NetLinx control systems.</p>
 
-<p>[todo: gem badge]</p>
+<p><a href="http://badge.fury.io/rb/netlinx-erb"><img
+src="https://badge.fury.io/rb/netlinx-erb.svg"></a> <a
+href="http://www.rubydoc.info/gems/netlinx-erb"><img
+src="http://img.shields.io/badge/docs-api-blue.svg"></a></p>
 
 <p>Syntax highlighting is included in <a
 href="https://github.com/amclain/sublime-netlinx">sublime-netlinx</a>.</p>
+
+<h2 id="label-Overview">Overview</h2>
+
+<p>Use a descriptive syntax…</p>
+
+<p><img
+src="https://github.com/amclain/netlinx-erb/blob/master/screenshots/example_erb.png"
+/></p>
+
+<p>To generate repetitive NetLinx code…</p>
+
+<p><img
+src="https://github.com/amclain/netlinx-erb/blob/master/screenshots/example_axi.png"
+/></p>
+
+<p>With netlinx-erb, configuration is separated from implementation. For
+example, touch panel button numbers and video inputs (configuration) are
+separated from the code that handles video patching when a button is
+pressed (implementation). Under this paradigm, reconfiguration can happen
+quickly as project requirements change. Since the implementation code is
+separated from these changes and code generation is automated, there is
+less chance of inducing bugs into the system when a change in configuration
+happens.</p>
+
+<p>For example, in the code above, let&#39;s say the client decides to add a
+camera to the system. All we have to do to update this file is add the
+following to the <code>video_sources</code> hash:</p>
+
+<pre class="code ruby"><code class="ruby">BTN_VID_CAMERA: { btn: 14, input: :VID_SRC_CAMERA }
+</code></pre>
+
+<p>This defines a new touch panel button constant <code>BTN_VID_CAMERA</code>,
+assigns that constant to channel number <code>14</code>, and adds a case to
+the button event handler to switch the video matrix to
+<code>VID_SRC_CAMERA</code> when the button is pressed. Since the
+implementation code for this change is auto-generated, and we know that the
+implementation code works correctly, it is unlikely that this change will
+create any bugs. There is a clear advantage to this method as the amount of
+code grows and the project becomes more complex.</p>
+
+<h3 id="label-RPC">RPC</h3>
+
+<p>A remote procedure call (RPC) mechanism is included to be able to call
+NetLinx functions through ICSLan (NetLinx Diagnostics, Telnet, etc.). To
+issue an RPC function call, <code>send_string</code> to
+<code>34500:1:0</code>. The body of the string should start with the name
+of the function, followed by a space-separated list of arguments.</p>
+
+<p>For the following function:</p>
+
+<pre class="code ruby"><code class="ruby">define_function patch_video(integer input, integer output)
+{
+    // Patch video matrix.
+}</code></pre>
+
+<p><code>patch_video 1 2</code> is the RPC string that would patch video input
+1 to output 2.</p>
+
+<h3 id="label-Backward+Compatibility">Backward Compatibility</h3>
+
+<p>The NetLinx files generated by netlinx-erb are designed to be fully
+backward compatible with traditional NetLinx project development, including
+readability and adequate whitespace. This means that any NetLinx programmer
+can take over maintenance of the project using the standard development
+tools provided by AMX and does not need to have any experience with
+netlinx-erb.</p>
+
+<p>It is important to note that <strong><em>this process is a one-way
+street</em></strong>. Once the generated files are modified by hand, the
+changes must be manually converted back to the template files or else they
+will be erased the next time the generator is run. Backward compatibility
+is designed for projects that are permanently passed to other programmers
+who are not familiar with netlinx-erb and are not able to learn it, like
+due to time constraints.</p>
+
+<h2 id="label-Issues-2C+Bugs-2C+Feature+Requests">Issues, Bugs, Feature Requests</h2>
+
+<p>Any bugs and feature requests should be reported on the GitHub issue
+tracker:</p>
+
+<p><a
+href="https://github.com/amclain/netlinx-erb/issues">github.com/amclain/netlinx-erb/issues</a></p>
+
+<p><strong>Pull requests are preferred via GitHub.</strong></p>
+
+<p>Mercurial users can use <a href="http://hg-git.github.io/">Hg-Git</a> to
+interact with GitHub repositories.</p>
+
+<h2 id="label-Installation">Installation</h2>
+
+<p>netlinx-erb is available as a Ruby gem.</p>
+<ol><li>
+<p>Install <a href="https://www.ruby-lang.org">Ruby</a> 2.1.5 or higher.</p>
+<ul><li>
+<p>Windows: Use <a
+href="http://rubyinstaller.org/downloads/">RubyInstaller</a> and make sure
+ruby/bin is in your <a
+href="http://www.computerhope.com/issues/ch000549.htm">system path</a>.</p>
+</li><li>
+<p>Linux: Use <a
+href="https://github.com/sstephenson/rbenv#basic-github-checkout">rbenv</a>.</p>
+</li><li>
+<p>Windows: Use <a
+href="http://rubyinstaller.org/downloads/">RubyInstaller</a> and make sure
+ruby/bin is in your <a
+href="http://www.computerhope.com/issues/ch000549.htm">system path</a>.</p>
+</li><li>
+<p>Linux: Use <a
+href="https://github.com/sstephenson/rbenv#basic-github-checkout">rbenv</a>.</p>
+</li></ul>
+</li><li>
+<p>Open the <a
+href="http://www.addictivetips.com/windows-tips/windows-7-elevated-command-prompt-in-context-menu/">command
+line</a> and type:</p>
+
+<p><strong><em>gem install netlinx-erb</em></strong></p>
+</li></ol>
+
+<p><em>NOTE: The NetLinx compiler executable provided by AMX, nlrc.exe, must
+be installed on your computer for this utility to work. It is included in
+the NetLinx Studio installation by default.</em></p>
+
+<p><strong>If you receive the following error when running gem
+install:</strong> <code>Unable to download data from https://rubygems.org/
+- SSL_connect returned=1</code></p>
+
+<p>Follow this guide: <a
+href="https://gist.github.com/luislavena/f064211759ee0f806c88">Workaround
+RubyGems’ SSL errors on Ruby for Windows (RubyInstaller)</a></p>
+
+<h2 id="label-Prerequisite+Knowledge">Prerequisite Knowledge</h2>
+
+<p>netlinx-erb is a complex utility and does have a learning curve. However,
+the time invested in learning this utility pays off in time saved from
+generating code that would otherwise be handwritten, and troubleshooting
+fewer bugs. Due to this, project maintenance also becomes easier.</p>
+
+<p>Basic experience with the <a href="https://www.ruby-lang.org">Ruby
+programming language</a> is required, as well as <a
+href="http://www.stuartellis.eu/articles/erb/">ERB templating</a>.</p>
+
+<h2 id="label-Getting+Started">Getting Started</h2>
+
+<h2 id="label-Code+Examples">Code Examples</h2>
 </div></div>
 
     <div id="footer">
-  Generated on Fri Jan 30 17:24:15 2015 by
+  Generated on Wed Feb 25 14:28:06 2015 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.8.7.6 (ruby-2.1.3).
 </div>

data/doc/top-level-namespace.html

@@ -105,7 +105,7 @@
 </div>
 
     <div id="footer">
-  Generated on Fri Jan 30 17:24:15 2015 by
+  Generated on Wed Feb 25 14:28:07 2015 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.8.7.6 (ruby-2.1.3).
 </div>

data/lib/netlinx-erb.rb

@@ -9,6 +9,14 @@ require_relative 'netlinx/erb/rpc'
 
 # :nodoc:
 module NetLinx
+  # NetLinx code generation.
   module ERB
   end
+  
+  # :nodoc:
+  module Rake
+    # NetLinx code generation rake tasks.
+    module ERB
+    end
+  end
 end

data/lib/netlinx/erb/rpc.rb

@@ -1,26 +1,3 @@
-# -----------------------------------------------------------------------------
-# The MIT License (MIT)
-
-# Copyright (c) 2014 Alex McLain and Joe McIlvain
-
-# Permission is hereby granted, free of charge, to any person obtaining a copy
-# of this software and associated documentation files (the "Software"), to deal
-# in the Software without restriction, including without limitation the rights
-# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-# copies of the Software, and to permit persons to whom the Software is
-# furnished to do so, subject to the following conditions:
-
-# The above copyright notice and this permission notice shall be included in
-# all copies or substantial portions of the Software.
-
-# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-# THE SOFTWARE.
-# -----------------------------------------------------------------------------
 
 require 'netlinx/workspace'
 
@@ -35,42 +12,42 @@ class RPC
       Does not have to exist.
     )
     ^(?<desc>[\t ]*\/\*(?:[^\*]|\*[^\/])*\*\/)?\s*
-
+    
     (?# Find the function definition. )
     define_function\s+
-
+    
     (?# Capture function's return type, if it exists.)
     (?<rtn>\w+(?<width>\[\d+\])?)??\s*
-
+    
     (?# Capture the function name. )
     (?<name>\w+)
-
+    
     (?#
       Capture the function parameters.
       Run this through another regex to get the type\\name pairs.
     )
     \(\s*(?<params>.*?)\s*\)\s*
-
+    
     (?# Capture the function's source code. )
     {[\r\n]*(?<code>(?:.|\r|\n)*?)?[\r\n]*}
     /x
-
+    
     param_exp = /\s*(?:(?<type>\w+)\s+(?<name>\w+(?<width>\[\d*\])?)),?\s*/
-
+    
     sections = {} # Collect a set of matches for each file, separated by file.
-
-
+    
+    
     # Pull file list from workspace.
-    workspace_path = Dir['*.apw'].first
-    workspace = NetLinx::Workspace.new file: workspace_path
-
+    workspace = NetLinx::Workspace.search
+    raise Errno::ENOENT, 'Workspace not found.' unless workspace
+    
     file_paths = workspace.projects.first.systems.first.files
       .map(&:path)
       .select { |path| path =~ /(\.axi|\.axs)$/ }
       .reject { |path| path =~ /rpc(?:-|_.*?)?\.axi/ } # Remove RPC files.
-
+    
     # file_paths = Dir['**/*.axi']
-
+    
     file_paths.each do |f|
       str = File.open(f.gsub('\\', '/'), "r:iso-8859-1").read
       matches = []
@@ -82,47 +59,47 @@ class RPC
       
       sections[f] = matches
     end
-
+    
     # -----------------------
     # Documentation Generator
     # -----------------------
-
+    
     # output = ''
     # sections.each do |name, matches|
-      
+    
     #   output << "--------------------------------------------------\n"
     #   output << "FILE: '#{name}'\n"
     #   output << "--------------------------------------------------\n"
     #   output << "\n\n"
-      
+    
     #   matches.each do |m|
     #     output << m[:desc].to_s
     #     output << "\n"
     #     output << m[:name].to_s
     #     output << "\n\n\n"
     #   end
-      
+    
     # end
-
+    
     # File.open('functions.axi', 'w+') { |f| f << output }
-
-
+    
+    
     # ----------------------
     # RPC Function Generator
     # ----------------------
-
+    
     # Generate list of included and excluded files for sanity check.
     directory_files = Dir['**/*.axi'] + Dir['**/*.axs']
-
+    
     included_files  = ''
     file_paths.each { |path| included_files << path.to_s.gsub('\\', '/') + "\n" } # TODO: As string.
-
+    
     excluded_files  = ''
     (directory_files - file_paths.map { |path| path.gsub '\\', '/' }).each { |path| excluded_files << path.to_s.gsub('\\', '/') + "\n" }
-
+    
     fn_symbols = [] # Symbol names to avoid duplicates.
     output = ''
-
+    
     output << <<-EOS
 (***********************************************************)
 (*                         WARNING                         *)
@@ -208,9 +185,9 @@ EOS
         
         fn_output << "#{fn[:name]}("
         fn_output << ");\n" if params.empty?
-
+        
         function_valid = false unless [nil, :integer].include? return_type
-          
+        
         # Generate parameters.
         param_index = 0
         params.each do |param|
@@ -247,7 +224,7 @@ EOS
         end
         
         fn_output << "        }\n\n"
-
+        
         # Store function string.
         if function_valid
           output << fn_output 
@@ -258,13 +235,13 @@ EOS
       end
       
     end
-
+    
     output << "    }\n"
     output << "}\n"
     output << "#end_if\n\n"
-
-
+    
+    
     File.open('include/rpc-functions.axi', 'w+') { |f| f << output }
   end
   
-end
+end