boardyuk has quit [Read error: Connection reset by peer]
zz_chrismcg is now known as chrismcg
boardyuk has joined #ruby-lang
boardyuk has quit [Read error: Connection reset by peer]
boardyuk has joined #ruby-lang
boardyuk has quit [Read error: Connection reset by peer]
boardyuk has joined #ruby-lang
tooky has joined #ruby-lang
tooky_ has joined #ruby-lang
tooky has quit [Ping timeout: 248 seconds]
s0ra_h is now known as sora_h
umttumt has quit [Remote host closed the connection]
cantonic has quit [Read error: Connection reset by peer]
cantonic has joined #ruby-lang
boardyuk has quit [Read error: Connection reset by peer]
tooky has joined #ruby-lang
boardyuk has joined #ruby-lang
jxie has joined #ruby-lang
tooky_ has quit [Ping timeout: 252 seconds]
<corecode>
o hi
<corecode>
is there a reasonable way to capture stdout/stderr/return code of a process, using array of strings to invoke, instead of shell interpreted string?
wpaulson has joined #ruby-lang
pajama has joined #ruby-lang
<yxhuvud>
ruby version?
<kvs>
corecode: Open3
<corecode>
yxhuvud: yea :/
<corecode>
yxhuvud: both?
<yxhuvud>
kvs: open3 on 1.8.7 doesn't handle return code.
<kvs>
I've been using 1.9 exclusively for the past couple of years - can't really remember much beside ruby-debug being broken
<banisterfiend>
henk: what's breaking for u
wpaulson_ has joined #ruby-lang
<henk>
banisterfiend: puppet mainly. Also there are no xmms2 bindings for ruby 1.9
<banisterfiend>
kvs: that's not a breakage in MRI though more a miscommunication and also disorganization
kaz_ has joined #ruby-lang
<banisterfiend>
henk: ah you were saying there was software broken on 1.9 rather than 1.9 being broken itself
<kvs>
banisterfiend: doesn't matter - between you and Mon_Ouie a better alternative has appeared :)
<banisterfiend>
kvs: oh you're talking about pry_debug ?
<kvs>
yeah
<banisterfiend>
cool, i didnt know people used that
<banisterfiend>
+1 Mon_Ouie :)
<henk>
banisterfiend: I consider ruby 1.9 broken when applications running fine in ruby1.8 don’t run in ruby 1.9.
<Mon_Ouie>
I still use it from time to time ;)
wpaulson has quit [Ping timeout: 240 seconds]
wpaulson_ is now known as wpaulson
<henk>
banisterfiend: But my point is mainly about the reasoning to use ruby 1.8, not about what is actually broken, ruby or software written in ruby.
<Muz>
Unfortunately, some of us still use 1.8.7 because it's the latest version supported on our /Enterprise/ systems.
<banisterfiend>
henk: you're wrong to think that :) 1.9 introduced backwards incompatible changes that were clearly documented and not that hard to fix
<banisterfiend>
henk: they've also had about 4 years to bring their software up to speed
<kvs>
banisterfiend: but maybe they should've bumped the version to 2.0
<banisterfiend>
henk: at this stage, it's entirely their fault
sora_h is now known as s0ra_h
<banisterfiend>
kvs: they just have a weird versioning scheme
<Muz>
On the topic of enterprise; at least Java manages to get backwards compatibility vaguely right.
wmoxam has quit [Ping timeout: 248 seconds]
<Muz>
Even though it's at the price of having new features, and moving at the speed of a comatose snail in treacle.
<kvs>
heh
<kvs>
but seriously, not calling it 2.0 is pretty bad
wmoxam has joined #ruby-lang
<kvs>
it's comparable to the whole PHP 5.2/5.3/5.4 mess
<banisterfiend>
kvs: i think they're going to start with a more intuitive versioning system after 2.0
<burgestrand>
hehe
<burgestrand>
"not this time, but next one!"
<banisterfiend>
hehe
kaz_ has quit [Remote host closed the connection]
<kvs>
didn't they already have that? as I understood it, 1.9 was supposed to be a dev-version, which just never really evolved into the 2.0 stable it should have been
<banisterfiend>
i dont remember the exact story
<banisterfiend>
i read it somehwere tho..
kaz_ has joined #ruby-lang
<kvs>
there was a Ruby 1.7 in between 1.6 and 1.8
<henk>
banisterfiend: As I said: I don’t care whose fault it is. And thanks for the correction on what I am supposed to think.
<banisterfiend>
henk: if someone doesn't upgrade their software for a new version of ruby which has been clearly communicated to have breaking changes, then the fault is on them. Esp. when they've had four years to do it.
tjadc has joined #ruby-lang
kristofferrr has quit [Quit: ❤]
<banisterfiend>
or maybe the fault is on you ;) if you're trying to run software that only says it's 1.8 compatible on 1.9 :)
<henk>
Or maybe … We just all have an opinion about that and think it is "clearly" the one everyone should have or he is "wrong to think that" …
<banisterfiend>
henk: Yeah, some people are still of the opinion the world is flat ;)
pajama_ has joined #ruby-lang
<henk>
Yeah, and some still think backwards compatibility really means being compatible with previous versions or that ruby is ruby …
<henk>
fools
s0ra_h is now known as sora_h
<banisterfiend>
henk: except they never said it was backwards compatible
<banisterfiend>
that's the point.
pajama has quit [Read error: Connection reset by peer]
<banisterfiend>
henk: 1.9 was said to introduce a few breaking changes
<banisterfiend>
1.9 is a major release, it's just an unorthodox versioning scheme. Would you feel the same if it was named ruby 2.0 ?
<henk>
So it’s not actually ruby anymore but ruby1.8 and ruby1.9, who knows if ruby 2.5 will still be related to ruby at all or maybe using python syntax? As long as it’s announced, everyone expecting it to be would be wrong, right?
<kvs>
also, why doesn't QEMM386 work with my Windows 7?
<banisterfiend>
henk: are you daft? you really think langauges aren't allowed to introduce breaking changes in major releases? that's the point of a major release
<banisterfiend>
henk: python 3 was even worse afaik, and nobody complains that "python 3 is broken" when their python 2.0 programs dont 'just work' on it
<kvs>
any major of PHP is the same, and now even the last three minors of php5 too
pajama_ has quit [Ping timeout: 255 seconds]
<Tasser>
banisterfiend, they should call it freakking ruby 1.10
zmack_ has joined #ruby-lang
zmack__ has joined #ruby-lang
zmack has quit [Ping timeout: 276 seconds]
<henk>
banisterfiend: Right, the point of every major release is to make changes breaking existing and working software. Way to go.
<banisterfiend>
henk: no, not the point. But that they're allowed to do that. It's an opportunity to get rid of mistakes and kruft from the past. For example, would you be happy if block variables in 1.9 were still lexical closures as in 1.8 ?
<banisterfiend>
it was a mistake in 1.8 and resulted in weird bugs
<banisterfiend>
henk: x = 3; (1..10).each { |x| } .. what should x be? The behaviour in 1.8 was broken, and needed to be fixed
zmack_ has quit [Ping timeout: 276 seconds]
<Hakon>
i don't get it, why does it say i'm banned here?
<banisterfiend>
similarly it was just plain creepy that block variables i 1.8 could be any kind of variable: (1..10).each { |@x| } worked
<Hakon>
atleast earlier today
<banisterfiend>
Hakon: because you hvae to login
<Hakon>
ah, getit
<Hakon>
i couldn't change my nick to my registered nick because of it
<Hakon>
:P
rolfb has joined #ruby-lang
<henk>
banisterfiend: It’s great that bugs get fixed. It’s not great that software gets broken.
boardyuk has quit [Read error: Connection reset by peer]
boardyuk has joined #ruby-lang
pemeon has joined #ruby-lang
<banisterfiend>
henk: except it wasn't a 'bug' it was a design flaw. I'm assuming 99% of the breaking changes you'er complaining about were design flaws that were subsequently fixed in 1.9
<workmad3>
henk: you can't always maintain backwards compatibility... that's why we have version numbers
<workmad3>
henk: and 1.9 was the first ruby since 1.0 that didn't manage to maintain backwards compatibility, iirc
<workmad3>
henk: and besides, it's hard to rant about 'what is ruby' when the standard for ruby is only just being formalised and I believe it's formalising around 1.9 ;)
<henk>
So to get back to the fault: the fault is "clearly" with the ruby programmers for designing a flawed language and now that that shit is fixed, the fault "clearly" got shifted to application developers? Clever.
<banisterfiend>
lol
<lzhz>
henk: while it is not great that software gets broken, it is sometimes a necessary trade-off.
pemeon has quit [Ping timeout: 248 seconds]
<banisterfiend>
henk: if i buy an upgraded lawn mower that is electric rather than petrol, you'd keep pouring petrol in it anyway, and start complaining when it doesnt work?
<banisterfiend>
you*
anildigital_work has joined #ruby-lang
<banisterfiend>
even though it says clearly on the box 'this is now an electric lawnmower, faster, more efficient, and cheaper'
<anildigital_work>
Is it good idea to use rescue one liner?
<anildigital_work>
or it should be always used with blocks?
<anildigital_work>
what do you say?
<Mon_Ouie>
It's a bad idea, it hides bug
<Mon_Ouie>
Specifically rescue the exception you care about when you need to
nofxxxx has quit [Ping timeout: 240 seconds]
<lzhz>
seconded
<henk>
banisterfiend: There is a saying in German, loosely translated it says "This comparison limps", and another one saying "Not everything that limps is a comparison" …
<banisterfiend>
henk: you're basically saying langauge developers have to relese a 'perfect' language first at 1.0? and after that they cant make improvements to it in subsequent major versions? Some improvements need to break backwards compatibility. The important thing is that those breakages aer clearly documented, which they were, and that it happens only in major releases, which is what ahppened here (1.9 was a major release).
<henk>
banisterfiend: So to answer your question: Yes, I would complain if the mower is still called exactly as my previous model with just the version number increased. And I actually do that for other products already.
<Mon_Ouie>
Are there any softwares that change name after introducing compatibility breaking changes?
<henk>
banisterfiend: I’m not. I’m saying that it’s easy for you to say the developers using ruby are at fault because they don’t fix their code, when it’s actually the ruby developers who made the mistakes in the first place.
<banisterfiend>
henk: Actually i think it's you who are at fault. I'm sure the developers of puppet never expected you to use it on 1.9 if it doesnt actually work on 1.9. Or do they say it's 1.9 compatible?
<banisterfiend>
If they actually said it's 1.9 compatible and it doesnt work there, then yes they're at fault.
<banisterfiend>
If they didnt' say i tworks on 1.9, and yet you are using it there, then it's you who are at fault. My guess is it's you. :)
<banisterfiend>
there's a table there saying not to use it with 1.9
Asher has joined #ruby-lang
<banisterfiend>
after that retarded little argument i feel a lot dumber, bbl after playing some doom 2
banisterfiend is now known as banister`doom
<henk>
banister`doom: oh, dumb me … I forgot to check the minor versions of the prerequisites. What a noob mistake. Everyone knows ruby isn’t ruby and libreoffice isn’t just libreoffice. My xmms2 client is not my xmms2 client either, with version 2.0 it will become an mpd client and only those reading the changelog will know muahaha
<henk>
banister`doom: Sorry you feel dumber, I’d have thought maybe you learned something from it …
toretore has joined #ruby-lang
toretore has quit [Remote host closed the connection]
pajama has joined #ruby-lang
<darix>
henk: people not reading the release notes of their tools are the same people who dont read the manual of their microwave and then try to dry their pets in it. and wonder if that doesnt give the results they expected.
pemeon has joined #ruby-lang
<henk>
darix: release notes != manual
<henk>
That comparison limps as much as the one about the lawn mower.
<darix>
i am sure the ruby docs mentioned the changes too
zmack__ has quit [Remote host closed the connection]
<yorickpeterse>
Still not pretty clear, Google usually gives a somewhat decent response message as to why a request failed
jxie has joined #ruby-lang
slyphon has joined #ruby-lang
<mfn>
Should the Gemfile be part of the gem itself?
<yorickpeterse>
Gemfiles go with the Gem, gemfile.lock does not
neocoin has joined #ruby-lang
<mfn>
ah .. thx
sepp2k1 has quit [Read error: Connection reset by peer]
yugui is now known as yugui_zzz
ttilley is now known as ttilley_off
solars has joined #ruby-lang
savage- has joined #ruby-lang
boardyuk_ has quit [Read error: Connection reset by peer]
boardyuk has joined #ruby-lang
headius has joined #ruby-lang
umttumt has joined #ruby-lang
apeiros_ has joined #ruby-lang
Rizzle has joined #ruby-lang
ViperMaul has quit [Ping timeout: 248 seconds]
vmoravec has quit [Quit: Leaving]
<asahi>
yorickpeterse: what can I provide to make it more clear?
<yorickpeterse>
Well for starters you could look at what response details Google gives back (in terms of error messages and such). Then you might want to check if there isn't some bug or rule in the proxy that prevents the particular request
coryf has joined #ruby-lang
boardyuk has quit [Read error: Connection reset by peer]
boardyuk has joined #ruby-lang
brianpWins has quit [Quit: brianpWins]
cha1tanya has joined #ruby-lang
<asahi>
yorickpeterse: okay. since the exact same code works on my local machine but not the remote one (the two also have the same ruby environment), I thought it was odd and maybe an issue with the port
jperry2_ has quit [Quit: jperry2_]
benjammin891 has quit [Ping timeout: 264 seconds]
jperry2_ has joined #ruby-lang
benjammin891 has joined #ruby-lang
arooni-mobile has quit [Read error: Connection reset by peer]
rolfb has quit [Read error: Connection reset by peer]
sora_h is now known as s0ra_h
rolfb has joined #ruby-lang
s0ra_h is now known as sora_h
tomb_ has joined #ruby-lang
benjammin891 has quit [Ping timeout: 240 seconds]
sora_h is now known as s0ra_h
s0ra_h is now known as sora_h
EvilJStoker has quit [Excess Flood]
tylergillies is now known as TheDoctor
symm- has quit [Ping timeout: 252 seconds]
TheDoctor is now known as TylerGillies
kirin` has joined #ruby-lang
jarib has quit [Excess Flood]
umttumt has quit [Remote host closed the connection]
jarib has joined #ruby-lang
savage- has quit [Remote host closed the connection]
malev has quit [Remote host closed the connection]
jperry2_ has quit [Quit: jperry2_]
ttilley_off is now known as ttilley
jperry2_ has joined #ruby-lang
dhruvasagar has quit [Ping timeout: 260 seconds]
banisterfiend has quit [Ping timeout: 260 seconds]
banisterfiend has joined #ruby-lang
boardyuk has joined #ruby-lang
brianpWins has joined #ruby-lang
jperry2_ has quit [Client Quit]
robin850 has joined #ruby-lang
carloslopes has joined #ruby-lang
<robin850>
Hello
<robin850>
I have a function which can take several arguments and a last one like this def foo(*bar, baz)
<robin850>
I want to set a default value on baz like this : def foo(*bar, baz = nil) but we can't with *bar. Does it exist a solution to solve this problem please ?
Fretta has joined #ruby-lang
malev has joined #ruby-lang
therod has joined #ruby-lang
Jay_Levitt has joined #ruby-lang
<apeiros_>
robin850: with foo(1,2,3), what value does baz have?
ttilley is now known as ttilley_off
mistym_ has joined #ruby-lang
mistym_ has quit [Remote host closed the connection]
boardyuk has quit [Quit: boardyuk]
<darix>
robin850: have baz before bar?
headius has quit [Quit: headius]
rockpapergoat has joined #ruby-lang
<Tasser>
can I tell CSV to parse fields as float?
<Tasser>
or to try to convert them?
headius has joined #ruby-lang
tommyvyo has joined #ruby-lang
savage- has joined #ruby-lang
tjadc has joined #ruby-lang
jtoy has joined #ruby-lang
Berglund has quit [Quit: Computer died.]
concernedcitizen has quit [Remote host closed the connection]
<apeiros_>
Tasser: yes. I don't remember how, but it's in the docs iirc
<Tasser>
apeiros_, converters: [:float]
<apeiros_>
you can either tell it to autoconvert all values or I think you can do it per column
<robin850>
apeiros_: with foo(1,2,3) baz == 3
concernedcitizen has joined #ruby-lang
concernedcitizen has quit [Changing host]
concernedcitizen has joined #ruby-lang
akira989 has quit [Remote host closed the connection]
pajama has quit [Remote host closed the connection]
<robin850>
apeiros_: It's more enjoyable for the chan too :)
carloslopes has quit [Remote host closed the connection]
<lianj>
young blood :)
pajama has joined #ruby-lang
<Mon_Ouie>
It's wrong in English, but not in all other "western languages"
<apeiros_>
well, with a space it is in all western languages
<apeiros_>
french uses a 1/4 space
<apeiros_>
if you want to typographically correct
<robin850>
apeiros_: Yes I'm french. I also put a space before a colon each time
<apeiros_>
the problem with a space is that it is breakable, so if it's at the end of the line, it might be wrapped to the next
<apeiros_>
the 1/4 space is also non-breakable
tenderlove has joined #ruby-lang
carloslopes has joined #ruby-lang
Hakon has quit [Quit: Leaving...]
ttilley_off is now known as ttilley
workmad3 has quit [Ping timeout: 240 seconds]
outsmartin1 has joined #ruby-lang
<Mon_Ouie>
The main problem is that most people don't have non-breaking space or the right quotes handy on their keyboards
levicole_ is now known as levicole
akira989 has joined #ruby-lang
outsmartin has quit [Ping timeout: 260 seconds]
Berglund has joined #ruby-lang
mwjcomputing has quit [Quit: Leaving]
salout has joined #ruby-lang
ruurd has quit [Quit: Leaving...]
JohnBat26 has quit [Ping timeout: 252 seconds]
Tref has quit [Quit: Tref]
pajama has quit [Remote host closed the connection]
dejongge has joined #ruby-lang
GarethAdams has quit [Quit: Leaving...]
mikeric has quit [Quit: mikeric]
chongyu123 has joined #ruby-lang
butchanton has joined #ruby-lang
tjadc has quit [Ping timeout: 255 seconds]
<apeiros_>
Mon_Ouie: yupp, which is why you generally just don't put a space
brianpWins has quit [Quit: brianpWins]
crudson has joined #ruby-lang
<Mon_Ouie>
I'm pretty sure we generally do, using the non-breaking one when available. When it actually matters, softwares would usually take care of that kind of formatting anyway.
GarethAdams has joined #ruby-lang
kaspernj_ has quit [Quit: Leaving]
gnufied has quit [Quit: Leaving.]
pajama has joined #ruby-lang
qpingu has joined #ruby-lang
dc5ala has quit [Quit: Ex-Chat]
outsmartin has joined #ruby-lang
slyphon_ has joined #ruby-lang
pajama has quit [Remote host closed the connection]
outsmartin1 has quit [Ping timeout: 276 seconds]
slyphon has quit [Ping timeout: 245 seconds]
neocoin has quit [Remote host closed the connection]
wmoxam_ has joined #ruby-lang
ruurd has joined #ruby-lang
outsmartin1 has joined #ruby-lang
outsmartin2 has joined #ruby-lang
slyphon has joined #ruby-lang
jtoy has joined #ruby-lang
cantonic has quit [Quit: cantonic]
bfreeman has joined #ruby-lang
outsmartin has quit [Ping timeout: 264 seconds]
slyphon_ has quit [Ping timeout: 245 seconds]
gsav has quit [Ping timeout: 264 seconds]
outsmartin1 has quit [Ping timeout: 276 seconds]
solars has quit [Ping timeout: 245 seconds]
EvilJStoker has quit [Excess Flood]
butchanton has quit [Quit: Leaving.]
gsav has joined #ruby-lang
kvirani has joined #ruby-lang
tjadc has joined #ruby-lang
sora_h is now known as s0ra_h
tenderlove has quit [Remote host closed the connection]
andrewhl has quit [Read error: Connection reset by peer]
Axsuul has joined #ruby-lang
andrewhl has joined #ruby-lang
tenderlove has joined #ruby-lang
cha1tanya has quit [Quit: आलोच..]
Guest10238 has joined #ruby-lang
therod has quit [Quit: (;д;)]
outsmartin has joined #ruby-lang
outsmartin2 has quit [Ping timeout: 255 seconds]
bfreeman has quit [Ping timeout: 276 seconds]
jackhammer2022 has joined #ruby-lang
jackhammer2022 has quit [Client Quit]
jackhammer2022 has joined #ruby-lang
snorkdude has joined #ruby-lang
<snorkdude>
How do I call a variable inside single quotes in Ruby?
<yxhuvud>
I'd call it a string
JohnBat26 has joined #ruby-lang
<snorkdude>
lol
<kristofferrr>
snorkdude: Concatenation.
<kristofferrr>
You can't use interpolation with single quotes.