palindrome program

Help? Yes. Do it for you? No. Post the code you have written so far.

this is the code i have done so far.the problem is every word i type,it shows it is palindrome.

Don't forget to chomp the $line variable to remove the return character.

Also, reverse on a scalar does a string reversal. So the split and join operation is extra work.

- Miller

Also, reverse on a scalar does a string reversal. So the split and join operation is extra work.

using split and join might be a requirement for the assignment. Someone posted the exact same assignment on another forum a couple of days ago. But the code on the other forum wasn't even close to getting it right.

here is the program .see whether it works out

nimisha,

While I know you think you are being helpful, simply providing the full script to the user, you are actually hindering their learning process. It is the policy of thescripts.com forum NOT to provide the answers to people's school work. Instead, we request that they post the code they are working on and help them to get it correct for what they are trying to do.

In the future, please work with the users code and refrain from the urge to just post the code they need.

Regards,

Jeff

tank you for the code,but the problem is, in the o/p after enetring the string nothing shows.that is the result is not known whether the enetred string is palindrome or not.

thank you guys for the support,ive solved the problem.here is the code for palindorme.

thank you guys for the support,ive solved the problem.here is the code for palindorme.

Good job! Thank you for posting your working solution and letting us know you solved your issue!

Regards,

Jeff

here is the program .see whether it works out

All that for a simple palindrome script? Well, it does adhere to the TIMTOWTDI philosophy of perl coding.

Or even this:

No real need for arrays.
Of course it's very good to know how to manipulate arrays like you are doing...

:)

Even better!! Hehehe (I'm having fun with this one)

I made use of the conditional statement where a comparison is followed by a "?"
the the code to be executed if true, followed by ":" and the code to be executed if NOT true. Very handy, only works for if else though. Can't have multiple things. elsif, elsif etc...

Notice that in PERL "else if" is actually written with one "e" missing. "elsif"
No typo.

Very handy, only works for if else though. Can't have multiple things. elsif, elsif etc..

Actually the ternary operator can have multiple conditions. Example:

here is the program .see whether it works out

It doesn't work. You have not loaded your subroutine into memory when you call on it at line 7. Also you have a typo (?) in your sub. ie:

The scalar $string hasn't been initialized.

Very interesting idea though. Cycle through the word comparing the first letter to the last, the second to the next to last etc... At least once you find an inequality the program will stop, NOT actually having to compare the whole statement. Could come in handy for comparing a very large file/scalar/array ect...

One other thing Wikipedia states that palindrome can be words, or phrases.

Actually the ternary operator can have multiple conditions. Example:

Expand|Select|Wrap|Line Numbers

1. my @nums = (23, 34, 77, 100, 61, 200, -3);
2. for (@nums) {
3. my $return = ($_ > 99) ? "$_ is over 99" :
4.                  ($_ > 49) ? "$_ is over 50 under 100" :
5.                  ($_ > 25) ? "$_ is over 25 under 50" :
6.                  ($_ > 0) ? "$_ is over 0 under 26" : "$_ is under zero";
7. print $return,"\n";
8. }  

What are the disadvantages if any to using the ternery operator?
Seems like a very good way to run comparisons.

Thanks Kevin!

Since it does the same thing as the if...elsif....else statement, I don't think there are really any dis-advantages, unless you are new to Perl and don't know what it is. You may have to field questions from them, but they will (hopefully) quickly catch on.

Regards,

Jeff

What are the disadvantages if any to using the ternery operator?
Seems like a very good way to run comparisons.

Thanks Kevin!

Good question. I am sure there are some disadvantages but I am not sure. As far as good perl coding practices go, the ternary operator should not be used for program flow control, for example:

$foo eq 'bar' ? do_this($foo) : do_that($foo);

But I don't know why that is I have just read it in some books. Probably something to do with using functions that return results in a void context, which is considered poor programming practice. Some people don't like the ternary operator just because it is harder to read for them instead of if/elsif/else blocks.

I tend to use it when the then/else part of the code is simple and short like the example code I posted. If the then/else part gets complicated, using more verbose code would be better.