> I think that's an attitude that most businesses do not share. Heck, I
> don't share that attitude when it comes to a business environment.
True, true.
> Speed is *never* an issue when it comes to correctness. I
> don't care for
> a fast, wrong answer.
Now that's beautiful prose!
> If line numbers are reported wrong, the tool is broken. And you can
> bent words in any way you want and declare it unclear
> implementation or
> "not really broken", for someone evaluating its use in the coorperate
> environment it's broken, and *his* opinion whether that's a bug or a
> feature matters. If you care about Perl playing a prominent role in
> many coorperation, you have to keep that in mind.
Abigail, you make a very good point. If we want to see Perl play the kind
of part in Corporate Business Ventures that it deserves, we need to see an
adaptation of sorts. As difficult as it may sound, the developing community
has to start thinking about its code from the business perspective. How,
exactly, this is achieved would be the underlying question of greatest
relevance. May I ask if you agree? I wonder what answers you have (and
everyone else of course) for this question, considering both the most
effective and the most possible solution.
- Tommy Butler
Atrixnet Web Development º ° º Tomorrow is Now.
web http://Atrixnet.com
email [EMAIL PROTECTED]
tel 8 1 7 . 4 6 8 . 7 7 1 6
fax 6 5 1 . 8 4 6 . 5 3 1 5
6711 Forest Park Drive º ° º Arlington, TX 76001
