Yes, I like the idea of #lang info(#lang setup/infotab) which is highly
constrained, and it is an out-of-box solution.
It's better to have a (get-info/file filename.rkt) as an alternative to
(get-info/full infodir-path).
On Thu, Nov 19, 2015 at 7:32 AM, Neil Van Dyke wrote:
> I generally second
On 11/18/2015 5:19 PM, Christopher Walborn wrote:
I'm looking for a way to read configuration files. The configuration file
format can be anything provided it's easily human readable/writable. I found
the ApacheConf solution on RosettaCode and may use that, but am wondering if
there is a conf
I generally second the idea of doing a configuration file format like
"info.rkt" (but not using that particular filename, unless your program
is tools for Racket development projects).
An advantage of this format is that you then have a few different
options for how to use the file. Specifica
info.rkt, that's its name, you can search it in docs for details.
On Thu, Nov 19, 2015 at 6:39 AM, Sam Tobin-Hochstadt
wrote:
> I usually use a file that I `read` and `write` with racket data,
> probably a hash table.
>
> Sam
>
> On Wed, Nov 18, 2015 at 5:19 PM, Christopher Walborn
> wrote:
> >
I usually use a file that I `read` and `write` with racket data,
probably a hash table.
Sam
On Wed, Nov 18, 2015 at 5:19 PM, Christopher Walborn wrote:
> I'm looking for a way to read configuration files. The configuration file
> format can be anything provided it's easily human readable/writab
I'm looking for a way to read configuration files. The configuration file
format can be anything provided it's easily human readable/writable. I found
the ApacheConf solution on RosettaCode and may use that, but am wondering if
there is a conf format that's more commonly used for Racket projects
6 matches
Mail list logo
