Activity Graph

Page 1 of 1


[01:28:21] pyrmont: has left #ruby: ()


[20:47:52] pyrmont: Read error: Connection reset by peer
[20:48:10] pyrmont: has joined #ruby


[12:01:07] pyrmont: emers3n: is a good site for practising different regex combinations to see which works for your situation.
[12:19:04] pyrmont: sheepman: Simplest is probably #include?
[12:27:26] pyrmont: Just run it twice?
[12:28:39] pyrmont: You can do more complicated things: do #select with a block and check the length of the result but that seems more obtuse to me.
[12:48:27] pyrmont: I don't think that'll work the way you expect. true && false will resolve to false and you'll just be checking for false.


[10:28:42] pyrmont: mememeIAMME: && has higher precedence and so your conditional won't work the way that you think it will. It's evaluating str[i] && i.odd? before it then calls include?. You need to put parentheses around str[i].
[10:29:59] pyrmont: No worries.
[10:30:17] pyrmont: Was just skimming the history.


[13:08:47] pyrmont: qolq: Like baweaver said, it's a little hard to know how best to structure this without more context but there are situations in which three values might be returned. The <=> method is typically implemented to return -1, 0, 1. My suggestion would be to return something in this format. Perhaps something like :constrained, :unconstrained, :unchanged.


[03:36:48] pyrmont: has joined #ruby


[17:39:28] pyrmont: samort7: I was looking for information about Enumerators the other day and found this article ( and its sequel helpful.
[19:10:26] pyrmont: *.net *.split


[12:22:11] pyrmont: @TomyLobo: It looks like it automatically switches. The request.rb file checks the value of Body#multipart? method and that just checks whether the params respond appropriately.


[07:50:38] pyrmont: has joined #ruby