A few months back, this blog’s monthly Exercise was to write a filter to reverse all text input<\/a>. No matter how much text floated in, the filter gobbled it all up and spewed it back in reverse order. This month’s challenge is similar, but on a smaller scale. As a filter, the program doesn’t prompt for input; it processes standard input until the EOF (end-of-file) is encountered. This operation means that text can be typed directly at the command prompt or redirected from a file or other source. As text is input, words are output backwards:<\/p>\n Due to line buffering<\/a>, the backwards text output occurs after the newline is input. Otherwise, each word is output backwards, including words with numbers and containing an apostrophe:<\/p>\n Above, the “word” Here’s sample output where a word with an apostrophe is processed:<\/p>\n Getting the basic word-reversing algorithm down is a first step. Adding tests for numbers and apostrophes can be added later, but it’s still part of the challenge.<\/p>\n Try this exercise on your own before you peek at my solution<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" sihT emit, eht retlif sesrever laudividni sdrow. Continue reading
\n
\nThe challenge this month is again to write a filter. This filter also reverses text, but only one word at a time.<\/p>\nThis is text input forwards - and backwards!
\nsihT si txet tupni sdrawrof - dna sdrawkcab!<\/code><\/p>\nWords with numbers abc123def
\nsdroW htiw srebmun fed321cba<\/code><\/p>\nabc123def<\/code> is processed and output as fed321cba<\/code>.<\/p>\nDon't try this at home!
\nt'noD yrt siht ta emoh!<\/code><\/p>\n