Skip to main content

Reverse program done with help (Ruby Program pt. 8)

On Tuesday night I went to the Ruby L.A. group and had a good time. Learned quite a bit. And the reverse program is done! So I described what I wanted to do and Evan, the group leader, had an even more elegant solution.

So my idea was (as I described in a previous post) to go through the line and read each character match it to the Unicode character-sets boundaries (using their hex-code numbers) and ingest it into an array in one or two or three character chunks per element. Then reverse the order of the elements in the array by passing them to another array and output that.

In the group I learned that arrays have a reverse method. So it's real easy to reverse them. But the coolest thing was how Evan proposed solving it.

Scan
Evan used the scan method (one I had heard about but haven't quite mastered) but here is the cool thing, by escaping the characters as Unicode the scan method basically does in one step what I wanted to do in many. Scan will spit out an array of elements that are split by whatever argument is fed to the scan method. You can have scan capture all the digits in a string, or in this case all the Unicode characters in a string. So scan check each element in order if it's a Unicode character (which all are going to be) it gets put into the array. Then I reverse the array and join it into a string again.

I had no idea you could use a Unicode Characters as an argument using what's called a regular expression. Which sound rather common and easy to understand but are in fact rather obtuse. They're a way of writing things the way the program sees them, but they are not intuitive or well explained in the books I have so far. So more on this later.

Right now the program works on any UTF8 file with no BOM(Byte Order Marking), something relatively easy to make on Notepad++.

Comments

Popular posts from this blog

How to configure Ubuntu's keyboard to work like a Mac's

Typing accents on a PC is a complicated Alt + three numbered code affair. One feels like a sorcerer casting a spell. "I summon thee accented é! I press the weird magical key Alt, and with 0191 get the flipped question mark!" For a bilingual person this meant that writing on the computer was a start-and-stop process. With Mac's it a whole lot easier, just Alt + e and the letter you wanted for accents and alt + ? for the question mark. No need to leave the keyboard for the number pad and no need to remember arcane number combinations or have a paper cheat sheet next to the keyboard, as I've seen in virtually every secretaries computer in Puerto Rico.

Linux has a interesting approach to foreign language characters: using a compose key. You hit this key which I typically map to Caps Lock and ' and the letter you want and voilá you get the accent. Kinda makes sense: single quotation mark is an accent, double gets you the ümalaut, works pretty well. Except for the ñ, wh…

Fixing Autocomplete in Github's Atom Text Editor for Ruby

I really like Github's Atom Text Editor. I really like that it's multi-platform allowing me to master one set of skills that is transferable to all platforms and all machines. 

On thing that just burns me of the default set-up in Atom is the Autocomplete feature that seems to change my words as a type them. Because Ruby uses the end of line as a terminus for a statement you usually finish a word with pressing the return button and you get really annoying changes to your finished typed word a la MS Word. I find myself yelling "No that's not what I wrote!" at the screen in busy coffee shops.

I disabled autocomplete for a while but it is a very useful function. Then I found out they changed the package that gave the autocomplete to a new one called "Autocomplete Plus" that gives you more options. All that I needed to change to make autocomplete sane again:

1. Open Atom's Preferences
2. Search the bundled packages for "Autocomplete Plus"

3. Go to t…

Contrasting Styles of Writing: English vs. Spanish

There is interestingly enough a big difference between what's considered good writing in Spanish and English. V.S. Naipul winner of the 2001 Nobel prize for literature publish an article on writing. In it he emphasizes the use of short clear sentences and encourages the lack of adjectives and adverbs. Essentially he pushes the writer to abandon florid language and master spartan communication. This is a desired feature of English prose, where short clipped sentences are the norm and seamlessly flow into a paragraph. In English prose the paragraph is the unit the writer cares about the most.

This is not the case in Spanish where whole short stories (I'm thinking this was Gabriel Garcia Marquez but maybe it was Cortázar) are written in one sentence. Something so difficult to do in English that the expert translator could best manage to encapsulate the tale in two sentences. The florid language is what is considered good writing in Spanish but unfortunately this has lead to what …