Camelia, the Perl 6 bug

IRC log for #mojo, 2012-12-09

| Channels | #mojo index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:02 ObseLeTe joined #mojo
00:06 sinkovsky joined #mojo
01:01 MikeD joined #mojo
01:15 Mike-PerlRecruiter_ joined #mojo
01:44 tempire I need an image hosting service with an api.  Something that can be used transparently.
01:51 tempire mobypicture.com
02:11 buu amazon s3
02:11 buu heh
02:15 * sri buys the oauth 2.0 book
02:18 sri look at that, yaws also has a book :o http://www.amazon.com/Building-Web-Appl​ications-Erlang-Working/dp/1449309968/
02:19 buu Erlang!
02:20 sri prolog syntax makes my eyes bleed
03:29 tempire I don't mind it.
03:29 tempire Except for the resource records
03:29 tempire that killed me
03:54 noganex_ joined #mojo
05:26 d4rkie joined #mojo
05:54 Foxcool joined #mojo
06:35 Vandal joined #mojo
07:17 sinkovsky joined #mojo
07:44 marcus Seems we've been in the Perl Japan Advent Calendar.
07:48 marcus I just contacted all the scott morrows I could find on twitter.
08:20 Adurah Perhaps the framework should've been a more pronounceable name...
08:21 suy Adurah: is easy to pronounce to me. But, to me, is hard to type mojolicio.us :)
08:21 Adurah Well, perhaps io.us is the domain that should've been used.
08:22 Adurah Not that it's available now...
08:22 Adurah suy, ye be Japanese?
08:23 suy Adurah: no. :-) Spanish.
08:23 Adurah Yeah, you'd be fine. :P
08:25 suy Yes, with a 26% of unemployment rate, we are suprisingly good. :-D
09:27 dod joined #mojo
09:45 alexeiras joined #mojo
09:46 dod joined #mojo
09:58 dabudabu joined #mojo
10:03 dpetrov_ joined #mojo
10:12 lammel2 joined #mojo
10:14 marcus memowe: need moar url_for? https://metacpan.org/release/MEMOWE/Mo​jolicious-Plugin-RelativeUrlFor-0.02/
10:21 rem_lex joined #mojo
11:06 sawtooth hmm, i'm trying to write a route to accept /?searchterm=blah
11:06 sawtooth the placeholders seem to ignore the '?'
11:09 Adurah Query strings aren't included, I think.
11:12 sawtooth i'm thinking they aren't also
11:12 sawtooth though almost certain i've done this before somehow *blink*
11:12 Adurah They're in $controller->param, perhaps other places...
11:14 kitt_vl joined #mojo
11:18 sawtooth yup.. just don't understand why Controller is 404'ing on this
11:18 sawtooth $r->get('/searchterm/:para​m')->to('example#search');
11:18 sawtooth URI is /searchterm/?string=blah
11:19 sawtooth shouldn't /?string=blah be the param ?
11:20 sawtooth when I query /searchterm/string=blah it behaves just fine
11:20 sawtooth guessing ? is handled differently
11:21 sawtooth i've also tried with wildcard placeholders.. no dice
11:22 dpetrov_ I think /searchterm/:Param would match /searchterm/something
11:23 dpetrov_ you want just get('/searchterm')
11:23 suy sawtooth: your url is   /?searchterm=foo  ? And is not working with  get '/'  ?
11:26 sawtooth ahhh yeah, vanilla route '/searchterm' and use $self->req->query_params to extract the query string will work for me
11:26 sawtooth thanks team :>
11:38 charsbar__ joined #mojo
11:39 perlite joined #mojo
11:52 rhaen joined #mojo
12:32 Foxcool joined #mojo
12:34 rhaen joined #mojo
12:52 marcus double rainbow sunday!
13:06 vervain joined #mojo
13:14 Mike-PerlRecruiter_ joined #mojo
15:11 dpetrov_ joined #mojo
15:15 Britzel_ joined #mojo
16:34 sri hmmm
16:34 sri new perltidy has some interesting new features
16:36 sri -sac would result in indentation like http://pastie.org/5502693
16:44 good_news_everyone joined #mojo
16:44 good_news_everyone [mojo] kraih pushed 1 new commit to master: http://git.io/q_1Gpw
16:44 good_news_everyone mojo/master 4fabfea Sebastian Riedel: cleaned everything up with new perltidy
16:44 good_news_everyone left #mojo
16:53 Britzel joined #mojo
17:21 * DaTa prefers http://pastie.org/5502850
17:27 dabudabu Me too. Assuming the space between on( and start wasn't done on purpose
17:31 sri DaTa: you have a perltidyrc for that?
17:33 sri i've tried writing one for that a few times now, but failed
17:33 sri the -sac version is the closest i got so far
17:34 DaTa sri: unfortunately not
18:11 sri our .perltidyrc currently generates this style http://pastie.org/5503029
18:13 sri http://pastie.org/5503042 # all styles for comparison
18:14 erema15 joined #mojo
18:23 vervain The '# Current Style' is how I typically write, or '#Documentation Style.  The last one for -sac rubs me up the wrong way.
18:47 xaka joined #mojo
19:06 jnbek joined #mojo
19:25 marcus sri: I prefer -sac to our style
19:29 dod joined #mojo
19:32 b2b joined #mojo
19:36 bc547 joined #mojo
19:38 sri http://pastie.org/5503349 # this is how mojolicious would change :)
19:38 sri marcus: you seem to be the only one
19:51 sri http://pastie.org/5503395 # a bigger example
19:58 dod joined #mojo
19:59 sinkovsky joined #mojo
20:10 marcus sri: with { } around the argument it looks bad
20:11 marcus ( {port => 3000} => sub { … }
20:11 sri ( (port => 3000) => sub { … }
20:11 sri that works too
20:22 tempire I go back and forth between # Doc and -sac
20:23 tempire right now I'm on the -sac side
20:24 marcus I like # Doc the bestest, but afaik it cannot be tidyed?
20:25 sri that's correct
20:25 sri the doc version is not really an option
20:26 sri actual options are to streamline everything to use the -sac version, or use -sac for code and keep the doc version
20:27 sri or of course, do nothing :)
20:28 sri i find it interesting that tempire doesn't prefer the doc version though
20:28 sri maybe a good sign
20:29 tempire given that on only takes one parameter/sub, the doc is fine.
20:30 tempire but when there are several, doc presents a visual inconsistency
20:30 sri very true
20:30 sri doc version is unrealistic
20:31 lukep joined #mojo
20:31 sri at first the -sac version did seem a bit odd to me too, but i think i'm already getting used to it
20:31 tempire I like it because it's lispy
20:32 tempire but beyond that, it's easy to follow if the code is not familiar
20:32 sri it's more like a multiline expression than a block now
20:34 marcus also more compact. I feel }\n) is wasteful
20:35 marcus so it seems we have 3+ for -sac?
20:35 sri seems so
20:35 sri i kind of like the idea to streamline documentation and code style
20:36 marcus I'm fine with that too
20:36 marcus unified gangnam style
20:36 marcus ;)
20:36 marcus I also use mojolicious perltidyrc on nordaaker projects.
20:36 marcus and on the batman project, even tho he hates perltidy in general :D
20:37 marcus oh wow, perltidy is hosted at sourceforge :-o
20:38 sri it's pretty damn old :)
20:39 sri also one of the reasons i like Go so much, it ships with it's own perltidy, gofmt
20:40 marcus gofmt yourself?
20:41 tempire I use mojolicious' perltidy as well.
20:41 tempire I had a customized version for a while, but then realized I didn't care enough to maintain it
20:41 sri also "go get http://github.com/becks/beer.git"
20:42 tempire why does batman hate perltidy?
20:42 tempire it's like the perfect thing
20:42 marcus tempire: he has weird ideas about craftmanship...
20:42 sri hand crafted bits
20:43 marcus mm
20:43 tempire I can understand that.  Sometimes I want this block of code to look just so.  But I'm learning that IT DOESNT MATTER SHIP THE CODE
20:45 marcus SHIP ALL THE CODE!
20:46 marcus https://i.chzbgr.com/completestore/​12/12/9/-9zczN8kwE-2Yw5PrJ2K6w2.jpg
20:47 marcus tempire: I prefer consistency to snowflake-code.
20:48 marcus also, it's a good excuse for writing sloppy coding style and letting the computer clean it up :)
20:48 rhaen joined #mojo
20:50 tempire Yes.
20:51 tempire Though, I do have an outlet for snowflake code.
20:51 marcus_ joined #mojo
20:51 tempire On my own throwaway projects, I'll spend 30 minutes trying to force many lines of code into one right->left map construct.
20:51 tempire sometimes hours.
20:52 tempire YOU WILL SUBMIT, code.
20:52 tempire left <- right
21:01 sri you might like the perl6 pipeline operator
21:02 marcus hellz yeah, I've beat jquery.terminal into submission. It will make an excellent irc input field.
21:02 marcus ctrl-r history search ftw
21:26 mmp joined #mojo
21:29 rem_lex|pivo joined #mojo
21:47 good_news_everyone joined #mojo
21:47 good_news_everyone [mojo] kraih created stack_all_containers (+1 new commit): http://git.io/F9XliQ
21:47 good_news_everyone mojo/stack_all_containers 8294c06 Sebastian Riedel: modernized ".perltidyrc"
21:47 good_news_everyone left #mojo
21:47 sri marcus, tempire, crab: that's everything that would change
21:49 b2b joined #mojo
21:52 tempire I really like ->each(sub {
21:52 sri it's an unrealistic example though
21:52 sri perltidy won't do that
21:53 tempire boo perltidy
21:53 sri i've noticed something else too
21:54 marcus someone has been stealing from the cookie jar?
21:54 sinkovsky joined #mojo
21:54 sri http://pastie.org/5503839 # -sac can look very inconsistent
21:54 sri i might be -1 on it now
21:55 marcus hmm, that looks good to me. :p
21:55 sri ;p
21:58 sri oh, they can also stack way further
21:58 sri https://github.com/kraih/mojo​/commit/8294c0611219#L30R300
22:02 marty joined #mojo
22:08 sinkovsky joined #mojo
22:09 alnewkirk joined #mojo
22:11 vervain ( first argument is way more natural than (\n in my opinion; but I also like my closing tokens to be at the same indentation level as my the line containing my opening token.
22:11 perlite joined #mojo
22:13 sri silly argument
22:16 sri http://pastie.org/5503936 # which one do you really prefer?
22:18 vervain Very much the latter... although I'd never do it.
22:18 vervain But I'd never do the former either
22:18 * marty waves
22:18 sri then what do you do?
22:18 sri o/
22:19 vervain That particular example would be one line.
22:19 sri pretend it is 82 chars long
22:20 vervain If it was enough arguments to justify more lines then it would be something based on the latter.
22:21 vervain I'm not really saying if it's right or not, just that my 'scan parsing' prefers the latter.
22:21 sri you're odd :)
22:24 vervain Absolutely! :-)
22:33 Britzel 2nd version is _mucho_ better.
22:33 Britzel Although I would prefer another , after the last argument.
22:34 Britzel I guess we are all odd, one way or other :)
22:44 marcus the oddest part is this whole discussion..
22:55 sri :)
22:58 tempire I use the first
22:58 tempire before perltiday
22:58 sri tempire: you still think the branch should be merged?
22:59 tempire I...
22:59 marcus perltoady
23:01 * tempire stalls
23:03 * sri injects some sodium penthathol into tempire's arm
23:04 tempire I'm ambivalent.
23:05 tempire I have no strong opinion either way.
23:05 tempire I don't know that it matters.
23:06 sri lets make it simple :)
23:06 sri http://pastie.org/5504132 # which one do you want, One or Two?
23:07 marty One looks more prettier   :)
23:09 tempire urg
23:10 tempire stick with one
23:10 sri heh
23:10 tempire you are right about the consistency
23:10 sri and i suppose we keep the documentation unrealistically formatted then
23:12 marcus "unrealistically"
23:12 marcus you can actually write that code you know :)
23:13 sri ;p
23:13 sri not with perltidy!
23:21 jzawodn joined #mojo
23:26 jberger joined #mojo

| Channels | #mojo index | Today | | Search | Google Search | Plain-Text | summary