Yesterday Dan McGinn-Combs wrote: > Honest! I wasn't trying to make trouble! :) > I just wanted to make sure my understanding was correct. I reckon it > isn't a limitation as long as the application knows to access _table > rather than a hash. > > The reason I was curious is that the DESCRIPTION at > http://isg.ee.ethz.ch/tools/realmen/down/data/ParseConfig.html shows > what looks like a section of hosts where the pointer to the array has > the same names as the contents of first column. But I may not have > understood relationship between the input and the output.
Hi Dan, hmm this depends if you specify one of the collumns as _key ... the cannonical location of this library is http://isg.ee.ethz.ch/tools/isgtc/index.cgi?page=module_pod;module=ISG_ParseConfig;pod=ISG/ParseConfig.pm the documentation might also be more current there ... I think the best way to get used to ISG::ParseConfig is to try some little examples ... hope this helps tobi > Dan > > -----Original Message----- > Today Dan McGinn-Combs wrote: > >> I noticed that there was apparently only one >> array called _table field permitted by the parser per section. Is this >> true? > > yes this is true ... how should the parser distinguisch between > different tables ? > > *** section *** > > a b c > 1 2 3 > > g k > 1 1 > > how about this ? > > *** another *** > +table1 > > l n p > 2 3 4 > > +table2 > > g k > 1 1 > > > -- > Unsubscribe mailto:[EMAIL PROTECTED] > Help mailto:[EMAIL PROTECTED] > Archive http://www.ee.ethz.ch/~slist/smokeping-users > WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi > -- ______ __ _ /_ __/_ / / (_) Oetiker @ ISG.EE, ETL F24.2, ETH, CH-8092 Zurich / // _ \/ _ \/ / System Manager, Time Lord, Coder, Designer, Coach /_/ \.__/_.__/_/ http://people.ee.ethz.ch/oetiker +41(0)44-632-5286 -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/smokeping-users WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
