srand() is not necessary in perl (as of 5.004, IIRC). rand is auto-seeded, and essentially you get the same seed as you did above without calling srand().
While people keep saying how Perl is insufficient to the task, thousands upon thousands of programmers will quietly, surely, quickly, efficiently, and superbly get their job done using it.
And since Harry Browne can't win, vote Bush! As Dennis Miller said after telling his audience to not be afraid to vote for third parties: "And let me know how that goes, because I am going to vote for whoever's gonna take less of my fucking money, OK?"
Slash (and Slashdot) runs on perl 5.005_03. It may run fine on perl 5.6. The current development branch of Slash, bender, is going to be tested on perl 5.6. We may upgrade Slashdot to perl 5.6 someday if it proves stable, or we might wait for perl 5.8.
Yeah, how DARE the GUY WHO RELEASED THE SOFTWARE warn people NOT TO USE IT without knowing exactly what they are doing, to counteract the original submissions saying "go upgrade now." Little wanker.
The key to OT performance is to respond to a network interrupt and pass pointers to a STREAMS message up the stack and back down again in less time than it takes to send a 1500 byte Ethernet packet. Since routing occurs at interrupt time, it is not affected by other applications.... And, its always nice to see the look on people's faces when you explain to them that your Mac is saving the planet by running rings around NT or Cisco routers and is way easier to configure than a linux machine!
What Simon says does matter, some. But not as much as what Sarathy, Larry, Chip, and Jarkko have to say (among other porters). And not as much as what Tom and Jon and others who have been around a long time have to say. Simon was wrong to post what he posted, and he knows it. Slashdot was wrong, I think, to post this at all. I don't know if they agree.
Sarathy is still involved (as mentioned on use Perl). I personally expect Tom to be involved with Perl, and would be surprised if he left. I have a sneaking suspicion that Ilya might be involved with it, too. He was at the meeting on Tuesday and seemed intrigued.
It is simply a matter of testing. We have not fully tested it, and it is not a high priority. We are planning to have bender, the development Slash, run on perl 5.6 (and in some future release, it might even require perl 5.6). But I wouldn't necessarily count on it happening, just because the priority for it is relatively low. There have been some accounts of breakage with some of the modules Slash uses (mod_perl, for instance), but I cannot say if anything in particular is broken.
Well, many things on CPAN _will break_ with perl 6. This is assumed. I apparently did not emphasize that enough in the original piece. Work will be done to make perl 5 stuff run in one way or another, but there will be breakage (probably would be greater between 5 and 6 than between 4 and 5).
You make it sound like everyone cannot go to the perl mailing lists now... they can. It is harder now, and yes, the barrier of entry is intended to be lower for perl 6.
I don't think it will be very transparent. I think a lot could and perhaps will change. Now, your old programs will still run, under perl 5 or some comaptibility mode in perl 6. But perl 6 will be different.
You cannot copyright what you did not create. You can possibly copyright the expression or form of the work, but not the data itself. You cannot patent what there is prior art for. The genome is mine, the data is mine, and you can't stop me from using it in any way I see fit.
Slashdot Mirror
srand() is not necessary in perl (as of 5.004, IIRC). rand is auto-seeded, and essentially you get the same seed as you did above without calling srand().
While people keep saying how Perl is insufficient to the task, thousands upon thousands of programmers will quietly, surely, quickly, efficiently, and superbly get their job done using it.
And since Harry Browne can't win, vote Bush! As Dennis Miller said after telling his audience to not be afraid to vote for third parties: "And let me know how that goes, because I am going to vote for whoever's gonna take less of my fucking money, OK?"
YAS has more info, see the story on use Perl.
BTW, I meant to add that I've run perl 5.6 on a machine with Slash and saw no problems.
Slash (and Slashdot) runs on perl 5.005_03. It may run fine on perl 5.6. The current development branch of Slash, bender, is going to be tested on perl 5.6. We may upgrade Slashdot to perl 5.6 someday if it proves stable, or we might wait for perl 5.8.
Yeah, how DARE the GUY WHO RELEASED THE SOFTWARE warn people NOT TO USE IT without knowing exactly what they are doing, to counteract the original submissions saying "go upgrade now." Little wanker.
The key to OT performance is to respond to a network interrupt and pass pointers to a STREAMS message up the stack and back down again in less time than it takes to send a 1500 byte Ethernet packet. Since routing occurs at interrupt time, it is not affected by other applications. ... And, its always nice to see the look on people's faces when you explain to them that your Mac is saving the planet by running rings around NT or Cisco routers and is way easier to configure than a linux machine!
And Photoshop or Lightwave on an Altivec-equipped Mac will blow away any other computer running any other OS. :p
What Simon says does matter, some. But not as much as what Sarathy, Larry, Chip, and Jarkko have to say (among other porters). And not as much as what Tom and Jon and others who have been around a long time have to say. Simon was wrong to post what he posted, and he knows it. Slashdot was wrong, I think, to post this at all. I don't know if they agree.
print while <>;
How about one better?
print <>;
Sarathy is still involved (as mentioned on use Perl). I personally expect Tom to be involved with Perl, and would be surprised if he left. I have a sneaking suspicion that Ilya might be involved with it, too. He was at the meeting on Tuesday and seemed intrigued.
It is simply a matter of testing. We have not fully tested it, and it is not a high priority. We are planning to have bender, the development Slash, run on perl 5.6 (and in some future release, it might even require perl 5.6). But I wouldn't necessarily count on it happening, just because the priority for it is relatively low. There have been some accounts of breakage with some of the modules Slash uses (mod_perl, for instance), but I cannot say if anything in particular is broken.
Well, many things on CPAN _will break_ with perl 6. This is assumed. I apparently did not emphasize that enough in the original piece. Work will be done to make perl 5 stuff run in one way or another, but there will be breakage (probably would be greater between 5 and 6 than between 4 and 5).
Slashdot uses perl 5.005_03.
Yes, well, that's the point. Filehandles already are, for the most part. In perl 5.6 you can do:
open my $fh, $path or die $!;
Formats, well, formats might go away entirely from the core and move to a more manageable, easy-to-use, sensical module.
Microsoft gives money to ActiveState to make Perl work better on Windows. ActiveState employs some key, core perl programmers.
Perl MAY have strong typing, but it would certainly be optional.
Yes, there is. Most of the core Perl developers call "5.005" "5.5".
You make it sound like everyone cannot go to the perl mailing lists now ... they can. It is harder now, and yes, the barrier of entry is intended to be lower for perl 6.
I don't think it will be very transparent. I think a lot could and perhaps will change. Now, your old programs will still run, under perl 5 or some comaptibility mode in perl 6. But perl 6 will be different.
Is that even possible?
As noted, a lack of copyright does not imply public domain. It implies the exact opposite.
However, since I own the data (as do the rest of us), it can't be copyrighted anyway. You might as well patent a smile or copyright a skin color.
You cannot copyright what you did not create. You can possibly copyright the expression or form of the work, but not the data itself. You cannot patent what there is prior art for. The genome is mine, the data is mine, and you can't stop me from using it in any way I see fit.
But ... it IS free.