This seems like a fine option:

#+name: mode_data
| mode       | paredit | auto-save |
|------------+---------+-----------|
| scheme     | TRUE    | TRUE      |
| emacs-lisp | TRUE    | TRUE      |
| ielm       | TRUE    | FALSE     |

#+begin_src emacs-lisp :var data=mode_data :exports results :file modes.json
  (require 'json)
  (json-encode data)
#+end_src

JSON because I will probably use it a few different ways, and most langs today handle JSON just fine.


On Tue, Feb 25, 2014 at 10:41 PM, Grant Rettke <gcr@wisdomandwonder.com> wrote:
Thanks everyone.

My tentative plan is to run some elisp that will dump the table to an
intermediate file and then dependent files may load it themselves.



--
Grant Rettke | ACM, AMA, COG, IEEE
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson