OC DelGuy, please stop shouting at us by using these huge letters and the red color.
Wp, I thought AllCaps meant shouting. I was just trying to soften the complaint. In my own head, I was trying to sound like Kevin Hart in his Satellite Radio commercials. Like when they come up to him and say "You don't have to listen to satellite radio in your car." And they give him a phone and he says "What?" Then they tell him he can hear it on his tablet. So he throws the phone away and says: "What?" Then a laptop and he tosses the tablet and says: "What?" Amazon Alexa and he tosses the laptop and says: "What?" In my mind, I sounded like him!
The "No!" was actually like a sing-song sarcastic no. I considered typing "Noooooooooooooo!!!", but that's like when you've fallen off a cliff. You yell out "Noooooooooooo!!" as you're falling.
The "Sys don't think so.", was a play on Damon Wayans' (is the name spelled right?) "Homie, the clown". His catch phrase was "Homie don't play that!"
So, don't sweat it, Wp. I was just being sarcastic! Trying to be funny. Just keeping my head from overheating and throwing my computer out the window. Wouldn't even go far... My window is inch-thick plexi-glass. It'd just bounce back and bonk me in the head!
Why don't you simply write what you were expecting and what you got?
Because I thought you'd see the same thing I did.
I ask the computer for the time (now), tell it to convert it into a string (DateToString), then tell it to convert it back into a datecode (StrToDate), which I know is a float (hence the 4.4!@#$%^&*E+004), and display it on the console (WriteLn).
And what I saw (the output) was basically like talking to my wife! I ask her what she wants from the supermarket (now). She writes it down on a piece of paper (DateToStr). I then tell her to look at the paper and ask: "What's that say?". And she turns around and tells me: "I can't read that. It's not formatted right! (this is the (StrToDate)) part. And then I'm like: "You wrote the darned note!!! And you're telling me it's in the wrong format??? You wrote it!!"
Oh Wifey, Wifey. If you could only hear what you say!
That's the "funny" part that's actually Bull$#!t.
My guess is that you wonder why the line "WriteLn(StrToDate(DateToStr(Now))" does not print a date but a number.
No sir, Wp. I wonder why I got the error that the format was wrong. That line was where I got the runtime error. That line didn't print on the console. You might have confused the output that Martin_fr showed. It seems to have worked on his computer, but not mine.
First of all: dates and floating point numbers are the same in Pascal. The date is the number of days past Dec 30 1899. The conversion function DateToStr(some_date) converts this number to a string formatted like a date (depending on details in your FormatSettings record). And StrToDate does the opposite: it takes a date-formatted string and converts it back to the count of days since Dec 30 1899.
The instruction "WriteLn(StrToDate(DateToStr(Now))" consists of four parts which are executed from the inside to the outside:
/1/ Now: determines the current date (and time) - always rember: as number of days sincd Dec 30 1899. This, for today, the value 44951. (The fractional part, BTW, represents the time between 0:00 and 24:00 - I am ignoring it here).
/2/ DateToStr(...): converts that day count to a nicely formatted date string, in your case probably '01/24/2023'
/3/ StrToDate(...): takes that date string and converts it back to date - but remember: date is just a number! So, the result is 44951
/4/ WriteLn(...): Prints this number. OK, since it is a floating point value the standard WriteLn() prints it in exponential notation. Nothing mystic here!
Yes, I know I ask a lot of questions here, But this I know.
The output of this sequence is absolutely correct.
Nope. It's not correct. It's also not incorrect. It's nothing, since it didn't even execute the line.
Your post is very confusing and it is not clear what the problem is.
And Here I will concede. You are correct. I included one thing that was irrelevant (the assembler dialog) when I should have taken the screenshot with the actual error message. My mistake. Had I included the error message, I believe it might not have been confusing.
Recent
