Anonymous user
Talk:Simple database: Difference between revisions
→does J use a human readable database?: new section
(→command line interface: I favor separation) |
(→does J use a human readable database?: new section) |
||
Line 9:
:well, one point of the task is to tie in other tasks like the use of serialization and also reading commandline options. i think building an interface on top of a REPL is worth a separate task: [[Readline interface]] (build a simple application with a readline interface.) the functionality of this program may be taken from [[Simple database]])--[[User:EMBee|eMBee]] 06:20, 2 November 2011 (UTC)
:: In general, the way I'd do it is to write a library that implements the functionality as a collection of procedures(/classes/whatever) and then an application or two that wraps that into a true command-line interface, an interactive shell, a GUI, a webapp, etc. as necessary. (Well, I wouldn't normally bother with writing an interactive shell as my preferred language already has one, but you get the picture.) Dividing functionality from (user-facing) interface makes testing much easier too. –[[User:Dkf|Donal Fellows]] 09:05, 2 November 2011 (UTC)
== does J use a human readable database? ==
could you please describe in more detail how the J solution meets the 'human readable database' requirement? the file containing the data itself should be directly readable without additional program support.
using a database dump would be acceptable if it is created every time the database is saved and read back in when the database is loaded.--[[User:EMBee|eMBee]] 03:46, 8 February 2012 (UTC)
| |||