--- In [email protected], "entropyreduction" <[EMAIL PROTECTED]> wrote: > > > Bruce has introduced line continuation, ;eval(), > ;include in cl ini files. > > I could emulate all that in the plugin service > ini.get_value, but it would be quite a bit of work. > > I wonder if anyone really needs ini plugin on cl ini > files. I can imagine using ini.write... services to > alter a cl ini file, but why would anyone need to read > one? > > Let me know if anyone can think of a reason to add > functionality to ini.read_value.
Hi Alan, You mean ini.get right? I've used the ini plugin quite a bit (but never for cl ini files). One issue I've discovered is that ini.set will happily write multiline content into a value, while ini.get will only return the first line of the same value. It seems to me that "get" should be able to return anything that "set" will put there. As such, perhaps "set" should give an error on multiline content. Otherwise, "set" (or an alternate function) should automatically alter multiline content before writing it to the ini, to conform to whatever multiline standard is adopted. I would like to point out that the Config::Inifiles Perl module uses Unix "here document" format for this purpose. If you update an ini value named "Parameter" with multiline content containing Line 1 Line 2 it ends up in the ini file looking like this: Parameter= <<EOT Line 1 Line 2 EOT There is a way to designate use of another string instead of EOT, but the beginning always gets the "<<" in front of it. When a multiline value is retrieved, the markers are not included. Maybe this would have been a good suggestion for Bruce as well. Regards, Sheri
