Hi Gabor,
* Gabor Szabo <[EMAIL PROTECTED]> [2007-03-28 17:35]:
> In line with the discussion of TAP I would like to show a use
> case I would like to be able to handle. I would like to be able
> to report certain information in table format in (or instead
> of) the diag call.
TAP is a protocol.
Andy Armstrong wrote:
>> That really requires me to collect all the data for this table and
>> then send it to diag. I think I would prefer to output it line by line
>> as the test runs, maybe with other calls in betwwen:
> [snip]
>
> Well of course there's nothing to stop anyone writing code that
On 28 Mar 2007, at 18:33, Gabor Szabo wrote:
On 3/28/07, Andy Armstrong <[EMAIL PROTECTED]> wrote:
On 28 Mar 2007, at 17:40, Andy Armstrong wrote:
> you'll probably do something like this:
>
> annotate( { dump => [EMAIL PROTECTED] } );
Actually there'll be another level below dump:
annotat
On 3/28/07, Andy Armstrong <[EMAIL PROTECTED]> wrote:
On 28 Mar 2007, at 17:40, Andy Armstrong wrote:
> you'll probably do something like this:
>
> annotate( { dump => [EMAIL PROTECTED] } );
Actually there'll be another level below dump:
annotate { dump => {'IP Table' => [EMAIL PROTECTED] }
On 28 Mar 2007, at 17:40, Andy Armstrong wrote:
you'll probably do something like this:
annotate( { dump => [EMAIL PROTECTED] } );
Actually there'll be another level below dump:
annotate { dump => {'IP Table' => [EMAIL PROTECTED] } };
--
Andy Armstrong, hexten.net
On 28 Mar 2007, at 16:32, Gabor Szabo wrote:
The output then can be in YAMLish or whatever but I would like to have
a parser that can generate HTML or whatever tables from this data.
Something like this:
---
| Name | IP
| Foo | 10.1.1.1
---
Sorry, that was half written only...
In line with the discussion of TAP I would like to show a use case I
would like to be able to handle. I would like to be able to report
certain information in table format
in (or instead of) the diag call.
So my test code would look something like this:
my $
