Buy premium account for $1.99 ($3.99)

Results for: literals 3

Create alert

Results 1 - 10 of 11 (found in 0.224s)

The Literals 002 2009 Steam

2009-05-29 - extension: cbr - size: 17 MB

The Literals 002 2009 Steam

The Literals #2 (of 3)

Hosted on: rapidshare.com

| Source: http://avaxhome.ws/magazines/comics/the_literals_2_of_3.html

Save to quick list - Download

FFMqlty2 - Taladrada Literal - RIPtato

2009-02-08 - extension: wmv - size: 2 MB

FFMqlty2 - Taladrada Literal - RIPtato

Hosted on: rapidshare.com

| Source: http://www.portalnet.cl/comunidad/showthread.php?t=69000&page=3

Save to quick list - Download

Literals 03 of 3 - The Great Fables Crossover 9 of 9 2009 Minutemen-Rosie

2009-07-22 - extension: cbr - size: 16 MB

Literals 03 of 3 - The Great Fables Crossover 9 of 9 2009 Minutemen-Rosie

Hosted on: rapidshare.com

| Source: http://projectw.org/viewtopic.php?f=62&t=742417&hilit=literals&start=1975

Save to quick list - Download

Video results for: literals 3More results from video

FFMPEG #75 FFmpeg Documentation
http://ffmpeg.mplayerhq.hu/ program You can integrate all the source code of the libraries to link (More)

Watch here

p6apclps #78 Perl 6 Apocalypse
http://www.perlfoundation.org/perl6 - - classes are now represented with C[[ [[...]] ]]. * (More) http://www.perlfoundation.org/perl6 - - classes are now represented with C[[ [[...]] ]]. * Grouping is now represented with C[[...]]. With these changes, and making better use of whitespace, the sample regex ends up looking like this: for ($text =~ m:ie[ name \: \h* (\N*?) \n \h* children \: \h* [ (\S+) [[,\h]]* ]* \n \h* favorite\ colors \: \h* [ (\S+) [[,\h]]* ]* \n ] ) { # now we have: # $1 = "John Abajace"; # $2 = ["Tom", "Dick", "Harry"] # $3 = ["red", "green", "blue"] } I think in the long run people will find this more readable once they're used to it. Certainly tabularizing the parallelisms will make any typing errors stand out. [Update: The ":ie" is now written ":i:g".] RFC 361: Simplifying "split()" The RFC makes five suggestions. I'll consider them one by one. *The first argument to split is currently interpreted as a regexp, regardless of whether or not it actually is one. (Yes, "split '.', $foo" doesn't split on dot -- it's currently the same an "split /./ , $foo".) I suggest that split be changed to treat only regexps as regexps, and everything else as literals.* Fine, I think. If the first argument to "split" is untyped, it should parse correctly, either evaluating a quoted string immediately or deferring interpretation of a regex. One could even do something like split on the first delimiter matched by another pattern: split _/(,|;)/; That would split on either all commas or all semicolons, depending on which it found first in the string. The _ forces the regex to return a string, which is whatever was captured by the parens in this case. [Update: "_" is now "~".] *Empty trailing fields are currently suppressed (although a -1 as the third argument disables this). I suggest that empty trailing fields be retained by default.* Probably okay, though we need a way to translate old code. It was originally done this way because split on whitespace would typically return an extra field after the newline. But most newlines will be prechomped in Perl 6. *When not in list context, split currently splits into @_. I suggest that this side-effect be removed.* Fine. It's easy enough to translate to an explicit assignment. *"split ?pat?" in any context currently splits into @_. I suggest that this side-effect be removed.* Fine. I don't think anyone uses that. *"split ' '" (but not "split / /") currently splits on whitespace, but also removes leading empty fields. I suggest that this irregularity be removed.* The question is, what to replace it with, since it's a very handy construct. We could use a different conventional pattern: @array = split /[ws]/, $string; Or we could say that it's now a split on whitespace only if the split argument is unspecified. That wouldn't work very well with the old syntax, where we often have to supply the second argument. But given that the "=~" operator now serves as a topicalizer for any term, we could translate: @array = split ' ', $string; to this: @array = $string =~ split; Oddly, this probably also works: $string =~ (@array = split); or maybe even this: @array = split given $string; But I think I like the OO notation better here anyway: @array = $string.split; In fact, split may not be a function at all. The default split might just be a string method and use unary dot: @array = .split; We still have the third argument to deal with, but that's likely to be specified like this: @array = $string.split(limit =] 3); We could conceivably make a different method for word splitting, much like REXX does: @array = .words; Then a limit could be the first argument: @array = .words(3); But there almost doesn't need to be such a method, since @array = m/ [ (\S*) \s* ]* /; will do the right thing. Admittedly, a ".words" method would be much more readable... Fortunately, "split" is a function, so I can put off that decision till Apocalypse 29. ":-)" [Update: At the moment I think there's a "words" multimethod on strings.] Rejected RFCs RFC 135: Require explicit m on matches, even with ?? and // as delimiters. Squish that gnat... ":-)" A decent Perl parser is still going to have to keep track of whether a term or an operator is expected. And while we're simplifying the grammar in many ways, it's also the case that we're letting users install their (Less)

Watch here