Skip Menu |

This queue is for tickets about the Config-Std CPAN distribution.

Report information
The Basics
Id: 16488
Status: open
Priority: 0/
Queue: Config-Std

People
Owner: Nobody in particular
Requestors: steven [...] knowmad.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: (no value)
Fixed in: (no value)



Subject: read in files with special seperators
Hadn't seen any response to my post under the old ticket (http://rt.cpan.org/NoAuth/Bug.html?id=14918), so I figured I'd move it to a new one. From: steven@knowmad.com Show quoted text
> Done. The next release will offer an option to control the default > separator: > > use Config::Std { def_sep => '=' }; > > Thanks for the suggestion. > > Damian >
To me it looks like you could then set the default seperator to anything you wanted... like say '-' or even '=>'. Would Config::Std read in files with special seperators if you set the seperator in the def_sep option? If not, then I would like to add that to the wishlist. :) Thnx for the great package. ~Steven
Date: Thu, 15 Dec 2005 06:44:11 +1100
From: Damian Conway <damian [...] conway.org>
To: bug-Config-Std [...] rt.cpan.org
Subject: Re: [cpan #16488] read in files with special seperators
RT-Send-Cc:
Show quoted text
> To me it looks like you could then set the default seperator to anything > you wanted... like say '-' or even '=>'. Would Config::Std read in files > with special seperators if you set the seperator in the def_sep option?
No. def_sep is only for output purposes. Show quoted text
> If not, then I would like to add that to the wishlist. :)
Sorry, but I'm not intending to add that functionality. The whole point of Config::Std was to force people to use one standard layout and syntax in config files. If I could have gotten away with it, I would have only allowed one separator. But it proved impossible to choose between : and = (half the people I asked wanted one, half wanted the other). Show quoted text
> Thnx for the great package.
Thnx for the kind words. :-) Damian