Actually, the code has always been broken and they don't have a clue how things get done today. They scurry around, spending money on this and that y2k consultant, whose experience includes how many previous millennium changes?
The code is broken. Yay.
Have you ever seen chewing gum and kite string keeping things running? It'll probably do the same come January.
The code is broken. It has always been broken. Nobody knows how to fix it. It shouldn't even work today; but, somehow,/. keeps us ontrack.
Keep up the good work. When you fix some code, feel free to post it to the list }:
I've tried to use gcc/egcs to build Perl for MSWin32-x86. For the most part, it works fine.
My most critical criterion, in a grossly heterogeneous environment (*NIX, OS/390, Tandem -- you name it, we're running it;), is the ability to ``write-once-run-anywhere''.
Unfortunately, I haven't been able to compile many of the modules thusly, such as the libwin stuff.
I've brought this up to perl5-porters and comp.lang.perl.misc; but, I've received only apologies and ``we'll get there eventually''.
Do any of you, dear readers, have truly Open Source Perl deployments running on wintel and *NIX? How do you compile modules?
Currently amassing my fortunes via architecting Distributed Systems Management for Fortune 100 companies, I'm constantly at the Management Tools portion of IT industry. Most amazing is how utterly intransigent these vendors are with responding to the needs of their customers. Sencondly, so many became millionaires selling this stuff; but, now the budding millionaires are those who take a hand in architecting, deploying and simply making it do something to address ROI concerns.
As long as this train keeps rolling, I guess I'll be paying the bills. But, it sure would be nice to run this stuff in my office }:-
Slashdot Mirror
privacy is an illusion and, clearly, you are hallucinating.
please, share whatever it is that you're on -- i haven't been that out of touch since they last cracked RSA . . .
Of course, the code is broken.
/. keeps us ontrack.
It is planned to be that way.
Actually, the code has always been broken and they don't have a clue how things get done today. They scurry around, spending money on this and that y2k consultant, whose experience includes how many previous millennium changes?
The code is broken. Yay.
Have you ever seen chewing gum and kite string keeping things running? It'll probably do the same come January.
The code is broken. It has always been broken. Nobody knows how to fix it. It shouldn't even work today; but, somehow,
Keep up the good work. When you fix some code, feel free to post it to the list }:
I've tried to use gcc/egcs to build Perl for MSWin32-x86. For the most part, it works fine.
;), is the ability to ``write-once-run-anywhere''.
My most critical criterion, in a grossly heterogeneous environment (*NIX, OS/390, Tandem -- you name it, we're running it
Unfortunately, I haven't been able to compile many of the modules thusly, such as the libwin stuff.
I've brought this up to perl5-porters and comp.lang.perl.misc; but, I've received only apologies and ``we'll get there eventually''.
Do any of you, dear readers, have truly Open Source Perl deployments running on wintel and *NIX? How do you compile modules?
I'll believe it when I see Tivoli:
;)
[a] directly support Linux; and
[b] go OpenSource
Currently amassing my fortunes via architecting Distributed Systems Management for Fortune 100 companies, I'm constantly at the Management Tools portion of IT industry. Most amazing is how utterly intransigent these vendors are with responding to the needs of their customers. Sencondly, so many became millionaires selling this stuff; but, now the budding millionaires are those who take a hand in architecting, deploying and simply making it do something to address ROI concerns.
As long as this train keeps rolling, I guess I'll be paying the bills. But, it sure would be nice to run this stuff in my office }:-