Ovid wrote:
--- Ken Williams <[EMAIL PROTECTED]> wrote:
If I were you I'd not use classes to model that part of it. Just
have
a Printer::Status::HP4500 (or HP::HP4500 or whatever) object with a
components() or consumables() method that returns a hash mapping name
to properties. E.g.:
"If you s
--- Ken Williams <[EMAIL PROTECTED]> wrote:
> Yeah, but if the method interfaces are going to be different for
> different printers (because they have different consumables), then
> you're going to have to use if($status->can('toner')) etc. instead of
> if(exists $status->{toner}) etc. I find th
On Dec 18, 2004, at 12:26 PM, Ovid wrote:
--- Ken Williams <[EMAIL PROTECTED]> wrote:
If I were you I'd not use classes to model that part of it. Just
have
a Printer::Status::HP4500 (or HP::HP4500 or whatever) object with a
components() or consumables() method that returns a hash mapping name
to p
--- Ken Williams <[EMAIL PROTECTED]> wrote:
> If I were you I'd not use classes to model that part of it. Just
> have
> a Printer::Status::HP4500 (or HP::HP4500 or whatever) object with a
> components() or consumables() method that returns a hash mapping name
> to properties. E.g.:
"If you say
On Sat, 18 Dec 2004, Terrence Brannon wrote:
David Landgren <[EMAIL PROTECTED]> writes:
The fact that it uses http is incidental. If HP bothered to supply a
half-decent MIB, SNMP would be a good alternative.
What does "MIB" stand for?
Men In Black. ;)
Oh, you mean the geek version... MIB stands f
David Landgren <[EMAIL PROTECTED]> writes:
> The fact that it uses http is incidental. If HP bothered to supply a
> half-decent MIB, SNMP would be a good alternative.
What does "MIB" stand for?
On Dec 17, 2004, at 4:02 PM, David Landgren wrote:
The biggest problem I see is how to avoid having to sketch out
everything up front. I think it's only after I get 3 or 4
Printer::Status::x::y modules under my belt that I'll *begin* to get a
feel for where the divisions lie and what methods can
