James Stroud kirjoitti:
>
>
>
> For instance, I have a copy_files section of a configuration. In order
> to know what goes with what you have to resort to gymnastics with the
> option names
>
> [copy_files]
> files_dir1 = this.file that.file
> path_dir1 = /some/path
>
> files_dir2 = the_othe
BJörn Lindqvist wrote:
> On 1/31/07, James Stroud <[EMAIL PROTECTED]> wrote:
>> [copy_files]
>> files_dir1 = this.file that.file
>> path_dir1 = /some/path
>>
>> files_dir2 = the_other.file yet_another.file
>> path_dir2 = /some/other/path
>>
>> In yaml, it might look thus.
>>
>> copy_files :
>>
On 1/31/07, James Stroud <[EMAIL PROTECTED]> wrote:
> [copy_files]
> files_dir1 = this.file that.file
> path_dir1 = /some/path
>
> files_dir2 = the_other.file yet_another.file
> path_dir2 = /some/other/path
>
> In yaml, it might look thus.
>
> copy_files :
> - files : [this.file, that.file]
>
James Stroud a écrit :
> Szabolcs Nagy wrote:
>
>>> Hurray for yaml! A perfect fit for my need! And a swell tool!
>>> Thanks a lot!
>>
>>
>>
>> i warn you against yaml
I feel both thanful, and sorry, for your warning. And not convinced
yet, but Ill be cautious.
>> it looks nice, but the underlying
On Jan 30, 8:06 pm, "Paddy" <[EMAIL PROTECTED]> wrote:
>
> Google for YAML and JSON formats too
>
YAML and JSON are good when used as data-interchange format, not as
configuration files.
These formats are too complex for non-programmers, so they will ask
aid for every editing ;)
I suggest ini-lik
Szabolcs Nagy wrote:
>>Hurray for yaml! A perfect fit for my need! And a swell tool!
>>Thanks a lot!
>
>
> i warn you against yaml
> it looks nice, but the underlying format is imho too complex (just
> look at their spec.)
>
> you said you don't want python source because that's too complex for
> Hurray for yaml! A perfect fit for my need! And a swell tool!
> Thanks a lot!
i warn you against yaml
it looks nice, but the underlying format is imho too complex (just
look at their spec.)
you said you don't want python source because that's too complex for
the users.
i must say that yaml i
Paddy a écrit :
>
> On Jan 30, 2:34 pm, Imbaud Pierre <[EMAIL PROTECTED]> wrote:
>
>>The applications I write are made of, lets say, algorithms and data.
>>I mean constant data, dicts, tables, etc: to keep algorithms simple,
>>describe what is peculiar, data dependent, as data rather than "case
>
On Jan 30, 2:34 pm, Imbaud Pierre <[EMAIL PROTECTED]> wrote:
> The applications I write are made of, lets say, algorithms and data.
> I mean constant data, dicts, tables, etc: to keep algorithms simple,
> describe what is peculiar, data dependent, as data rather than "case
> statements". These co
Imbaud Pierre wrote:
> Larry Bates a écrit :
>> Imbaud Pierre wrote:
>>
>>> The applications I write are made of, lets say, algorithms and data.
>>> I mean constant data, dicts, tables, etc: to keep algorithms simple,
>>> describe what is peculiar, data dependent, as data rather than "case
>>> stat
Larry Bates a écrit :
> Imbaud Pierre wrote:
>
>>The applications I write are made of, lets say, algorithms and data.
>>I mean constant data, dicts, tables, etc: to keep algorithms simple,
>>describe what is peculiar, data dependent, as data rather than "case
>>statements". These could be called c
Szabolcs Nagy a écrit :
>>The lazy way to do this: have modules that initialize bunches of
>>objects, attributes holding the data: the object is somehow the row of
>>the "table", attribute names being the column. This is the way I
>>proceeded up to now.
>>Data input this way are almost "configurati
> The lazy way to do this: have modules that initialize bunches of
> objects, attributes holding the data: the object is somehow the row of
> the "table", attribute names being the column. This is the way I
> proceeded up to now.
> Data input this way are almost "configuration data", with 2 big
> d
Imbaud Pierre wrote:
> The applications I write are made of, lets say, algorithms and data.
> I mean constant data, dicts, tables, etc: to keep algorithms simple,
> describe what is peculiar, data dependent, as data rather than "case
> statements". These could be called configuration data.
>
> The
The applications I write are made of, lets say, algorithms and data.
I mean constant data, dicts, tables, etc: to keep algorithms simple,
describe what is peculiar, data dependent, as data rather than "case
statements". These could be called configuration data.
The lazy way to do this: have module
15 matches
Mail list logo
