Skip to main content

Scope and Rookie Mistakes (My first ruby program p.4)

Imagine a master clock-maker. He sits on a specialized wooden desk surrounded by empty bins on which he puts the parts of clocks he makes or repairs. Behind him is the eager young assistant. The assistant is great and helpful and will look for any tool the master needs, so the master can concentrate. And concentrate he will. He puts on his magnifying glasses, and starts to work. The assistant not only fetches tools but also clears up bins around the master that he is not using. The assistant knows one key thing about the master. He can only focus on one object at once. If he's working on a gear that's all he knows. If he's working on a mechanism that's all he knows.  His magnifying glasses obscure the vision around him so he won't notice something next to him if it's not in his field of view. That's kind of how Ruby works. The field of view at any time is the scope. When the master puts what's his working down and says he's done the assistant swoops in and takes that stuff away.

On my first program I immediately made a mistake on scope that I sort of stumbled to solving but now I know why what I did worked. When I ran the original program I ran into an error: undefined local variable or method 'text'.
"Hmm not defined?" I thought; so I went ahead and added this line to the top text = to define it. But this is unnecessary. The problem I was running into was that I had put a puts statement after I told the assistant I was done. The assistant came by and removed the text variable I had just created. Then after it was cleared, I wanted to access it again with puts. The master clock maker looks around sees no text variable and spits out an error.

"What text? What is this text? You kids and your texting..." he says.

This also meant that I only displayed text after the loop had finished and so probably would only show one file (the last one) instead of all. As you see once I put the puts text back into the block (do..end) it works, even without the text = line.


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…

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 …

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…