Buy premium account for $1.99 ($3.99)

Results for: ages of apocalypse

Create alert

Results 1 - 10 of 51 (found in 0.324s)

AgeofApocalypse

2009-12-19 - extension: rar - size: 152 MB

AgeofApocalypse

Age of Apocalypse (Complete)

Hosted on: rapidshare.com

| Source: http://www.tinydl.com/ebooks/137916-age-of-apocalypse-complete.html

Save to quick list - Download

official handbook of the marvel universe - x-men - age of apocalypse 2005

2009-07-19 - extension: rar - size: 22 MB

official handbook of the marvel universe - x-men - age of apocalypse 2005

OHTMU-Age of Apocalypse

Hosted on: badongo.com

| Source: http://www.badongo.com/en/file/582593

Save to quick list - Download

Age of Apocalypse Complete Run

2009-05-04 - extension: rar - parts: 7 - size: 98 MB

Age of Apocalypse Complete Run

Hosted on: rapidshare.com

| Source: http://planetsuzy.org/showpost.php?p=827710&postcount=1

Save to quick list - Download

Video results for: ages of apocalypseMore results from video

2012-Apocalypse or New Sun? - Shift of the Ages
In the ancient cities of the Maya, Grand Elder "Wandering Wolf" talks about 2012, the end (More)

Watch here

p6apclps #22 Perl 6 Apocalypse
http://www.perlfoundation.org/perl6 - - This RFC proposes long names as aliases for the various (More) http://www.perlfoundation.org/perl6 - - This RFC proposes long names as aliases for the various filetest operators, so that instead of saying: -r $file you might say something like: use english; freadable($file) Actually, there's no need for the "use english", I expect. These names could merely universal (or nearly universal) methods. In any case, we should start getting used to the idea that "mumble($foo)" is equivalent to "$foo.mumble()", at least in the absence of a local subroutine definition to the contrary. So I expect that we'll see both: is_readable($file) and: $file.is_readable Similar to the cascaded filetest ops in the previous section, one approach might be that the boolean methods return the object in question for success so that method calls could be stacked without repeating the object: if ($file.is_dir .is_readable .is_writable .is_executable) { [Update: the syntax above is now illegal.] But "-drwx $file" could still be construed as more readable, for some definition of readability. And cascading methods aren't really short-circuited. Plus, the value returned would have to be something like "$file is true," to prevent confusion over filename "0." There is also the question of whether this really saves us anything other than a little notational convenience. If each of those methods has to do a *stat* on the filename, it will be rather slow. To fix that, what we'd actually have to return would be not the filename, but some object containing the stat buffer (represented in Perl 5 by the "_" character). If we did that, we wouldn't have to play "$file is true" games, because a valid stat buffer object would (presumably) always be true (at least until it's false). The same argument would apply to cascaded filetest operators we talked about earlier. An autoloaded "-drwx" handler would presumably be smart enough to do a single stat. But we'd likely lose the speed gain by invoking the autoload mechanism. So cascaded operators (either "-X" style or ".is_XXX" style) are the way to go. They just return objects that know how to be either boolean or stat buffer objects in context. This implies you could even say $statbuf = -f $file or die "Not a regular file: $file"; if (-r -w $statbuf) { ... } This allows us to simplify the special case in Perl 5 represented by the "_" token, which was always rather difficult to explain. And returning a stat buffer instead of $file prevents the confusing: $handle = open -r -w -x $file or die; Unless, of course, we decide to make a stat buffer object return the filename in a string context. ":-)" RFC 283: "tr///" in array context should return a histogram Yes, but ... While it's true that I put that item into the Todo list ages ago, I think that histograms should probably have their own interface, since the histogram should probably be returned as a complete hash in scalar context, but we can't guess that they'll want a histogram for an ordinary scalar "tr/ //". On the other hand, it could just be a "/h" modifier. But we've already done violence to "tr///" to make it do character counting without transliterating, so maybe this isn't so far fetched. One problem with this RFC is that it does the histogram over the input rather than the output string. The original Todo entry did not specify this, but it was what I had intended. But it's more useful to do it on the resulting characters because then you can use the "tr///" itself to categorize characters into, say, vowels and consonants, and then count the resulting V's and C's. On the other hand, I'm thinking that the "tr///" interface is really rather lousy, and getting lousier every day. The whole "tr/// " interface is kind of sucky for any sort of dynamically generated data. But even without dynamic data, there are serious problems. It was bad enough when the character set was just ASCII. The basic problem is that the notation is inside out from what it should be, in the sense that it doesn't actually show which characters correspond, so you have to count characters. We made some progress on that in Perl 5 when, instead of: tr/abcdefghijklmnopqrstuvwxyz/ VCCCVCCCVCCCCCVCCCCCVCCCCC/ we allowed you to say: tr[abcdefghijklmnopqrstuvwxyz] [VCCCVCCCVCCCCCVCCCCCVCCCCC] There are also shenanigans you can play if you know that duplicates on the left side prefer the first mention to subsequent mentions: tr/aeioua-z/VVVVVC/ But you're still working against the notation. We need a more explicit (Less)

Watch here