| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
Comments:
<0> yes, like, take a value and return it mutated? How unusual:)
<1> not really
<1> it's called imperative programming.
<2> dynsfunctional programming!
<2> dysfuncitonal
<2> damn can't type
<3> dyndns-functional ?
<4> dynamic functional programming
<0> eval: my @penis = ("stuff", "chomp\n", "likes\n\n", "to", "eat\n"); my @smegma = grep { chomp } @penis; [@{[@smegma]}]
<5> avar: ['chomp','likes ','eat']
<0> I was feeling silly close to the end, apologies
<4> whatdaya know! http://w3.ualg.pt/~jmcardo/MyPapers/samos04a.pd
<3> well, it gave me a use-case for chomp's return value, anyway :)
<0> but the return value of chomp is neat to find out ... what the return value of chomp is on certain input
<6> feeling very silly today, avar?
<3> shift8: not much, if one goes by return codes
<0> dec: very,
<3> s/return/status/
<0> dec: I think I might go for a silly ... walk?
<6> avar: sounds... silly!
<7> what happes if you have /\Q$foo\E/ and $foo is '\E.*'?
<0> ryan_: OMGEXPLOIT!
<4> http://www.google.com/url?sa=t&ct=res&cd=7&url=http%3A%2F%2Fw3.ualg.pt%2F~jmcardo%2FMyPapers%2Fsamos04a.pdf&ei=as22RJTYBKLOpwLskYzFDA&sig2=kLLqsB0rO95pYewfemdHvg
<8> shift8's url is at http://xrl.us/o3wm
<9> it matches the string '\E.*'
<7> ok
<0> /\Q\\E\.\*\E/
<3> shift8: i was wondering what kind of file is a .pd ... silly me
<7> ah....
<10> hmmmmmmm
<7> I figured it was probably smart enough to do that.
<7> whereas if this were php somehow your hard drive would be formatted.
<4> kulp: well, there's pure data files, but that was surely a typo...
<10> when sigils are used for deferencing, should they be considered prefix operators?
<10> tightly bound prefix operators to be sure
<10> but operators
<10> butt operators.
<10> *laff*
<4> kulp: someone mentioned earlier today a fpga implimented perl interp, that link covers a basic for that (and based on merlyn's typo :)
<3> shift8: thanks, looks interesting
<2> smooth operator. :)
<11> I am back like crack!
<2> what typo?
<4> dynsfunctional programming!
<2> oh
<4> :)
<10> merlyn.
<2> heh
<2> hey tera
<10> greetings and felicitations
<2> tera "patrick" togen
<10> tera "tony" togen
<10> =D
<10> so did you catch my question about sigils as prefix operators, merlyn?
<2> nope
<10> when sigils are used to dereference, shouldn't they be considered prefix operators?
<10> (tightly bound ones)
<2> nope
<10> I would think, yes.
<2> any more than the () in "if" are "operators"
<10> they are operating on a reference
<2> it's just part of the syntax
<10> well, operators are part of the syntax too
<2> right.
<2> but they don't really have a "precedence"
<10> so I guess it's a question of what we mean by "operating upon"
<2> in a traditional way
<10> you agree that [] and {} are outfix operators
<2> Uh - no, I don't agree to that
<1> *sigh*
<1> today is _NOT_ my day
<1> ****ing awfully at nethack
<10> thought we had talked that one out, merlyn
<0> what the hell is on outfix?
<0> *an
<2> it's circumfix without the spelling mistakes
<10> merlyn made the term "outfix" up on the spot
<0> heh
<0> I like it better
<10> [] operates on expr in [ expr ] to create a reference to an array
<10> hence, "outfix"
<2> I think it falls in the same category as () though
<2> or maybe not
<2> I think "operator" should be reserved to things that are in the precedence table
<4> hear hear
<2> and outfix things don't really have a precedence
<2> since there's never an ambiguity as to what they attach
<10> but sigils that are used to dereference do, the highest precedence
<2> uh - no they don't
<10> well, yeah
<10> $$$foo
<2> ... $$foo[$bar] is ${$foo}[$bar]
<2> not $($foo)[$bar]
<2> you can't write the latter
<10> oh
<2> it's not valid
<2> that's why it's *syntax* not an operator
<10> I was just thinking about what it means to be an operator
<2> or even a smooth operator. :)
<10> "being in the precedence table" is not a satisfactory answer, afaiac
<2> ... http://flightaware.com/live/flight/QXE2553
<10> you know what's really smooth is one tablespoon of metamucil mixed with a can of V-8 tomato juice
<10> goes down smooth, lots of fiber
<10> where are you flying to?
<0> @$foo[0 .. 1]
<2> the reverse of that flight. :)
<10> oh
<0> the one case where @$ makes sense:)
<2> that plane just bounces back and forth all day
<0> Perl 6 will be different
<2> *very* different
<0> no I mean in this regard, i.e. %$foo<bar> not %{$foo{bar}}
<2> is %$foo legal?
<2> the hash pointed at by $foo?
<2> $foo<bar> is the same as %$foo<bar> :)
<4> merlyn:will twigils be required in p6?
<0> merlyn: yes
<10> I still think that in $$foo, the first $ operates on $foo, which contains a reference, to yield a scalar variable
<0> shift8: yes
<10> hence $ is an operator
<2> $$foo means ${ $foo }
<7> Variable length lookbehind not implemented in regex; marked by <-- HERE in m/(?<!(\\\\)*\\)\s+ <-- HERE
<2> it's just syntax
<0> shift8: those are not twigils however
<7> is there any fix for that?
<7> or workaround?
<2> ryan_ - don't do variable length llookbehind
<2> that's the fix
<10> ok merlyn
<0> twigils are stuff like $?LINE
<0> I really like those b.t.w.
<12> ryan_: alas :(
<2> how the hell is it suppsoed to know where to start the lookbehind?
<2> except all possible places
<2> trying all possible combos
<4> avar: i wasn't talking about t and merlyns conversation
<2> until ONE of them ends up at your start point
<12> merlyn: yes, all possible places! :)
<2> maybe in a quantum universie? :)
<12> If they have variable length lookbehinds in some other universe, I'll move there
<2> beth - I know you're calling. :)
<2> mindbob talks too damn much
<2> can we ban him, please?
<1> haha
Return to
#perl
or
Go to some related
logs:
#mysql
xorg User level driver support
suse installation_sources cat
mysql ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)
can't find multipathd redhat
what doesspinlock bad magic mean
#python
imq fc5
how do I shut down xserver ubuntu
linux intel536 amd64
|
|