How I can zerofy the day and month. I like to add 0 in the beginning.
Now an object cannot have 0 at the beginning unless it is a string
object in this context.
My code:
class Fixnum
def zerofy!
self < 10 ? '0' + self.to_s : self.to_s
end
end
t = Time.at(time.to_i)
day,month,year = t.to_a[3..5]
month.zerofy!
Does Time.at(time.to_i).strftime('%d/%m/%Y') do what you want?
--MarkusQ
···
On Wed, 2005-05-25 at 14:25, aartist wrote:
How I can zerofy the day and month. I like to add 0 in the beginning.
Now an object cannot have 0 at the beginning unless it is a string
object in this context.
Try something like
def zerofy!
sprintf("%02d", self)
end
V
aartist wrote:
···
How I can zerofy the day and month. I like to add 0 in the beginning.
Now an object cannot have 0 at the beginning unless it is a string
object in this context.
My code:
class Fixnum
def zerofy!
self < 10 ? '0' + self.to_s : self.to_s
end
end
t = Time.at(time.to_i)
day,month,year = t.to_a[3..5]
month.zerofy!
I think the real problem here is that maybe you aren't quite comfortable
with the typing system. Fixnums are designed for mathematical
manipulation. Strings (in this context) are generally used for display. So
basically you want to hold off on converting to a string for as long as
possible. Generally, there's no need to do an explicit conversion. You'll
generally just use printf or something when you need to display it, but
you'll keep the integer as the actual object.
On Wed, 25 May 2005 14:24:17 -0700, aartist wrote:
How I can zerofy the day and month. I like to add 0 in the beginning.
Now an object cannot have 0 at the beginning unless it is a string
object in this context.
The code you posted works, but it may not be doing what you think it
should. Specifically, Fixnum#zerofy! returns the string you want, but
it doesn't cause the recipient to _become_ that string (since the
recipient is a Fixnum, this would involve heavy Juju and is not what
you'd what, even if you think it is). You may have mislead yourself by
sticking a bang! on the end.
--MarkusQ
···
On Wed, 2005-05-25 at 14:45, aartist wrote:
Thanks that does the trick.
I still like to make zerofy working, just to understand the concepts.
I still like to make zerofy working, just to understand the concepts.
That method works for me.
irb(main):002:0> class Fixnum
irb(main):003:1> def zerofy!
irb(main):004:2> self < 10 ? '0' + self.to_s : self.to_s
irb(main):005:2> end
irb(main):006:1> end
=> nil
irb(main):007:0> 5.zerofy!
=> "05"
So I don't think your problem was where you think it is. By the way,
just as a point of style, since this isn't changing the Fixnum or doing
anything out the the ordinary really, I don't think the method ought to
have a bang on the end.
I am newbie in Ruby, but I am interested in that heavy juju, you
mentioned.
The juju is too heavy. Bulk up on some lighter juju first. (Using the juju when you are a newbie implies that you are probably trying to do something you're not supposed to do.)
ri Fixnum : gives me two important thing.
A. Fixnum objects have immediate value
B. You cannot add a singleton method.
I would like to know, if you can add destructive method to Fixnum
objects..
Since Fixnum objects are immediate, you can't make any changes to them.
Is it not possible?
I am newbie in Ruby, but I am interested in that heavy juju, you
mentioned.
ri Fixnum : gives me two important thing.
A. Fixnum objects have immediate value
B. You cannot add a singleton method.
I would like to know, if you can add destructive method to Fixnum
objects..
You really don't want to do that. You would be changing the meaning of
the number 5 for every operation afterward. You'd see cases like this:
(begin mock code)
month = 5 #=> 5
month.zerofy! #=> "05"
Timmy.age = 5 #=> "05" #It's Timmy's birthday!
Timmy.age += 1 #ERROR! You can't add 1 to a String, which is what
zerofy! turned 5 into
(end mock code)
Keep in mind that methods do not operate on the variables you use to
call them. Variables are just references to objects, any several can
refer to the same object. Every call to the number 5 goes to the same
Fixnum object. Besides it being incredibly evil (in the Evil Ruby
sense) to transform an object into one of a completely different type,
doing so to the number 5 is a particularly diabolical concept.
Keep in mind that methods do not operate on the variables you use to
call them. Variables are just references to objects, any several can
refer to the same object.
I like to say it like this: Languages like Java and C++ encourage you to
think of variables as boxes into which you put values. In Ruby, variables
are postit notes (with names) that you stick on objects.
···
--
-- Jim Weirich jim@weirichhouse.org http://onestepback.org
-----------------------------------------------------------------
"Beware of bugs in the above code; I have only proved it correct,
not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)