<leftylink>
ah. in fact... so line 8 . make it print operator.inspect instead of just operator. that will probably shed some light on your situation.
Cork has joined #ruby
<leftylink>
just printing operator isn't showing the full extent of your situation, whereas operator.inspect will make it clear
<leah2>
kinda mean that puts hides the bug :)
<leftylink>
okay, true. another way it could be done is if line 8 were: puts "operator value: >>>>> #{operator{ <<<<<"
<leftylink>
oops, wrong brace
<leftylink>
okay, true. another way it could be done is if line 8 were: puts "operator value: >>>>> #{operator} <<<<<"
<Wafficus>
interesting
<Wafficus>
so there's an understood newline character
<Wafficus>
is this a known Ruby-ism in that case then?
<Wafficus>
or is it the fact that I have multiple '\n' sections present in the 'puts' statements?
<leftylink>
gets simply returned the string as it were to you,k so if there were something to be known beforehand, it's knowing this behaviour of gets
<Wafficus>
hmm I see
Rounin has joined #ruby
<Wafficus>
I still don't know why I can't just use that operator variable though
<Wafficus>
its weird
<Wafficus>
unless there's a 'char' data type instead of a string or something
<leftylink>
well. "+\n" != "+"
<Wafficus>
for sure, that I get
<Wafficus>
gets always interprets the output plus a newline characer then?
<Wafficus>
*character?
<leftylink>
well, think about it... if gets removed characters like whitespace, then you'd be losing information (whether those characters were originally there)
teclator has joined #ruby
<Wafficus>
I gotcha, so am I doing string input wrong or something
<Wafficus>
I feel like there's something weird or missing in this workflow
<leftylink>
without a definition of "right" or "wrong" to work with, we couldn't really the answer "am I doing it wrong". in terms of how someone using ths calculator would expect to be able to provide input to it, it seems entirely reasonable for them to expect that they are responding to the calculator's prompts line by line, pressing enter when they are done with each. therefore, you would conclude that gets is
<leftylink>
entirely appropriate for the situation.
<Wafficus>
got it, should have been just using 'chomp'
<Wafficus>
gets.chomp specifically
<Wafficus>
kind of wish someone just said that, come on guys
ur5us has joined #ruby
Wafficus has quit [Quit: Connection closed]
<leftylink>
I will reflect and return with a more mature image (think about when it would have been appropriate to bring up chomp)
<leftylink>
I think it would have been inappropriate to bring it up before the querent had understood the nature of the problem (there was a newline), but it would have been appropriate at any time after that. due to my mistake, I got distracted by philosophical questions instead of bringing it up at that point.
<leftylink>
easily distracted by philosophical questions
dohtem has quit [Quit: Connection closed for inactivity]
krishnac has joined #ruby
sleetdrop has joined #ruby
BSaboia has joined #ruby
Oxfuxxx has joined #ruby
krishnac has quit [Ping timeout: 240 seconds]
Bounga has joined #ruby
Tempesta has quit [Quit: See ya!]
BSaboia has quit [Quit: This computer has gone to sleep]
Tempesta has joined #ruby
Guest1229 has joined #ruby
Guest1229 has quit [Quit: Leaving]
pip_ has joined #ruby
BSaboia has joined #ruby
pip_ has quit [Ping timeout: 265 seconds]
Oxfuxxx has quit [Ping timeout: 256 seconds]
pip_ has joined #ruby
pip_ has quit [Ping timeout: 240 seconds]
BSaboia has quit [Quit: This computer has gone to sleep]
sleetdrop has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
BSaboia has joined #ruby
shlomo has quit [Ping timeout: 265 seconds]
Oxfuxxx has joined #ruby
Bounga has quit [Ping timeout: 252 seconds]
BSaboia has quit [Quit: This computer has gone to sleep]
BSaboia has joined #ruby
reset has joined #ruby
BSaboia has quit [Quit: This computer has gone to sleep]
menace has joined #ruby
menace has quit [Changing host]
menace has joined #ruby
BSaboia has joined #ruby
menace has left #ruby [#ruby]
taupiqueur has joined #ruby
constxd has joined #ruby
BSaboia has quit [Quit: This computer has gone to sleep]
BSaboia has joined #ruby
BSaboia has quit [Quit: This computer has gone to sleep]
BSaboia has joined #ruby
BSaboia has quit [Client Quit]
Oxfuxxx has quit [Quit: Never underestimate the power of the butt..[]X/O...ON. (Playst...i mean.. Pir@tA$$)]
Oxfuxxx has joined #ruby
dohtem has joined #ruby
TomyWork has joined #ruby
<TomyWork>
how common is Net::LDAP? is it like the go-to gem for LDAP that's used by most applications with LDAP support? or is there something more or similarly widespread?
<adam12>
I don't personally use LDAP, but there's this library as well, depending on your requirements: simple_ldap_authenticator
<adam12>
It does wrap Net::LDAP tho.
Bounga has joined #ruby
BSaboia has joined #ruby
BSaboia has quit [Remote host closed the connection]
taupiqueur has quit [Quit: taupiqueur]
_ht has joined #ruby
Bounga has quit [Ping timeout: 256 seconds]
riffraff has quit [Quit: Client closed]
riffraff has joined #ruby
riffraff has quit [Quit: Client closed]
riffraff has joined #ruby
riffraff has quit [Ping timeout: 256 seconds]
___nick___ has joined #ruby
TomyWork has quit [Remote host closed the connection]
roadie has joined #ruby
cornduck has quit [Remote host closed the connection]