Skip Menu |

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

Report information
The Basics
Id: 62096
Status: resolved
Priority: 0/
Queue: Config-General

People
Owner: tlinden [...] cpan.org
Requestors: alex [...] cluonflux.com
Cc:
AdminCc:

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



Subject: Retain original source of configuration values
I'm using Config::General to parse Apache configuration files, and it works very well for that purpose, except that I'd love to be able to identify, after the fact, which file a given item originated with. Since C::G's output is a plain old hash, I guess there's no room in the result for that kind of metadata. I suppose one way to do this could be a parallel structure; more generally, if there were some way to "hook" C::G so I could be notified on various kinds of events I could roll my own. Thanks!
Well the thing is, that C::G needs to be rewritten from scratch for such stuff. And there are more bugs/feature requests, which lead to this. So, I'm considering rewriting it and using an OOP aproach for the internal structure which retains original files, line numbers, comments, uninterpolated variable contents and the like. But this takes time, since the module is widely used and I just can't do such a heavy change without causing much damage to users.
From: Alex
On Wed Feb 01 03:41:02 2012, TLINDEN wrote: Show quoted text
> I'm considering rewriting it and using an OOP aproach for the internal > structure which retains original files, line numbers, comments, > uninterpolated variable contents and the like. But this takes time, > since the module is widely used and I just can't do such a heavy change > without causing much damage to users.
I ended up switching to Augeas anyway, but thanks for C::G, it got me off the ground quickly. :)
closed then.