| |
| |
| |
|
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 29 30 31 32 33 34 35 36 37
Comments:
<0> anyone know ? I am sort of confused about how the || differs then in C++
<0> or if there is any differences
<1> 1st by hand, 2nd by P::RD (part A, using stratification and left-recursion elimination, part B using P::RD shortcuts, part C using right recursion and reversing the tree)
<1> 3rd using Lex/Yacc
<1> 4th using the techniques in HOP
<1> and 5th - if I get around to reading the dragon book - anything in there that I haven't already covered
<2> jonx: 2 || 0 is 1 in C++, 2 in Perl
<3> jonx: the operators return what made them true/false.
<3> erm, the one that cauesd them to short-circut.
<0> mauke, hmm so in this above though in which $aws can be 'A', 'W', or 'S', then next if $aws ne 'A' || $aws ne 'W'; this should always prove true
<0> but it doesn't for some reaosn
<2> jonx: testcase?
<2> $x || $y: $x ? $x : $y; $x && $y: $x ? $y : $x
<3> mauke: well said.
<3> although less `:'s would have made it clearer
<4> this is one fierce storm
<4> dozens of lightning strikes, many within a mile of me
<3> japhy: do you have a tape back up?
<1> japhy - fierce and big too
<1> you are in NJ right
<4> ok, that one was probably 3000 feet away
<4> yeah, near princeton
<4> HUGE line of thunderstorms
<4> wow, those are right on top of me.
<1> I am in MD and we are getting very big lightning ATM
<1> I lost power
<1> luckily I have a big UPS
<1> ;-)
<4> Limbic_Region: biking your way onto IRC? ;)
<4> I just have a surge protector, but I don't have anything terribly valuable on my computer here at home
<5> is there a pastebot here?
<2> yes
<0> www.rafb.net
<0> really annoying fat boy --> rafb
<4> Limbic_Region: where in MD are you?
<1> 21113
<4> I have a sister who lives in parkville
<1> well - pretty ignorant of all geography for that matter
<4> parkville's a couple miles off 95 on the northwestern half of the baltimore beltway
<1> oh, doesn't sound too far
<4> ok. THAT was the oddest thunder I've ever heard
<4> 30 miles, says google
<1> 29.6 says yahoo
<3> in the car, we'll find out for ourselves!
<4> 29.8
<4> I was in MD briefly for memorial day weekend
<4> but only to transfer to her car and drive down to franklin, virginia
<5> can someone look at http://www.rafb.net/paste/results/d0onud75.html for obvious errors, please?
<6> The paste d0onud75 has been moved to http://sial.org/pbot/17510
<2> tinny: use warnings; use strict;
<4> tinny: don't do 'for (<FH>)'
<4> do 'while (<FH>)'
<4> it's smarter than the average bear
<2> tinny: line 6: missing open mode
<4> and don't use printf() when you just want to print.
<2> tinny: line 6, 7: add $! to die
<4> I haven't heard a fire truck yet, which is good
<4> ouch.
<1> japhy - you ever wonder why lightning is jagged and not straight
<5> what package is all that open stuff in?
<1> electricity doesn't only follow the path of least resistance, it follows all available paths simultaneously, the current however is inversly proportional to the resistance
<7> Because the path of least electrical resistance changes as the lightning goes from the earth up to the clouds?
<2> tinny: huh?
<5> Global symbol "$outfile" requires explicit package name...
<1> Martyn - something like that
<2> tinny: you shouldn't use global anyway
<2> *globals
<7> Limbic : The downward burst of electrons that we can acutally see, is following the conductive path set up from the upward strike...
<7> The good 'ol glowing air :)
<4> yes yes.
<5> it's a pretty short hack, don't think global usage is gonna spin me out of control
<4> this is the best thunderstorm I've seen in a few years
<7> Limbic_Region : Your solution has been done via chemistry .. the DNA solver to the problem :)
<2> tinny: just use local variables
<3> Limbic_Region: the solution ``electricute the salesman'' isn't a solution to the traveling salesman problem
<4> tinny: your variables are global. you should make them lexical. declare them in their outermost scope with 'my'.
<7> Using dna cutters and polymerase reactions L:)
<5> my $infile etc?
<1> Martyn - interesting - I knew it was possible but didn't know it had been done
<4> I just saw some amazing cloud-to-cloud lighning
<1> got a link?
<4> tinny: yes.
<1> f00li5h - heh
<8> Limbic_Region: How would that solve the problem? You'd still have to hit every link right?
<1> buu - all paths are tried simultaneously
<1> you then would just have to measure the current to know which is the shortest (least resistant)
<7> Limbic : put "DNA travelling saleseman" into google for a bunch of results
<1> of course - I don't know enough to know if that actually works
<8> Limbic_Region: Doesn't really seem to be a "solving" it so much as a different way to brute force it
<5> it's still just echoing output
<1> buu - ok, but it is solved at the speed of light
<8> heh
<5> my regex is not doing anything to help me
<7> Limbic_Region : More slowly
<7> Electrons flow at far slower than the speed of light.
<7> They have m***, after all.
<4> repost your code, tinny. let's see what it looks like
<4> Martyn: I think there's one or two differences, tops.
<8> Martyn: %INC
<2> do doesn't check for errors and can load files more than once
<2> buu: bzzt
<5> http://www.rafb.net/paste/results/gHHLMz37.html
<6> The paste gHHLMz37 has been moved to http://sial.org/pbot/17511
<1> Martyn - I am ***uming 0K
<5> that's the latest mess :)
<8> hrm
<8> eval: keys %INC
<6> buu: Return: 229
<8> heh
<2> buu: oops, no. I'm doing it wrong :(
<8> mauke: Figures.
<1> Martyn - either 0K or room temperature super-conductivity
<4> tinny: it looks good to me, except you're still using printf() when print() will do just fine.
<8> require throws the error again but do doesn't
<5> japhy, the regex does not seem to be working.. it matches every time
<5> no, it's not
<5> it's being very very greedy
<1> ok, brain fry is at just the right level of crispy
<1> I am out
<1> TTFN all
<5> ok, thanks for your helps
<5> stupid mac line breaks were wreaking havoc
<5> coupled with inexperience...
<4> tinny: I was gonna suggest you didn't have "lines"
<5> i figured that one out on my own, after looking at the output forensically
<5> that it was being a really greedy match gave me the clue
<9> GumbyBRAIN: Perl owns
<10> Generally, people who have attempted to help it to changing the hash that is owns.
<9> cube it
<11> Mmm, post-apocalyptic flannel.
<4> eww. ugly ugly bug on perlmonks. :(
<3> workbench: the best kind.
<11> Couldn't find a verb in that.
<4> http://www.perlmonks.org/?node_id=553184
<8> japhy: I need a way to distinguish STDOUT from return values.
<4> buu: hrm?
<12> hy. can anyone help me with a regex to cut hours out of "Time : 23:07 UTC"
<4> yure: do you know how to match the time?
<12> yes
<12> let's suppose i have only "23:07 UTC" to make things simpler
<9> I can't even login to perlmonks
<9> I've forgoten my p***word. And the email ***ociated with my account is dead.
<4> yure: the point is, if you can match the HH:MM part, you should be able to replace it with just the MM part
<4> or, if by "cut" you meant "extract"...
<12> i mean extract :)
Return to
#perl
or
Go to some related
logs:
suse msttf fonts
kuvkir
#javascript
libssl.so destest error while loading shared libraries
#suse
mcpu emt64
#asm
ssh command mount f xbox ubuntu
#osdev
tinyfugue background bot
|
|