excerpted from caro's journal: topic: perl

go to caro's entire journal
view entire entry:
2001_05_21:18: Pah

to see pictures, view entire journal
perl
respond
responses
When I finally figure out what I am working on, I am going to put an explanation of it on the web. This will piss everyone off, as no one yet has seen fit to provide an explanation of it. There always seems to come a point in working with computers where people don't want to tell you how to do something, and it seems that the only reason is that then they wouldn't be the only ones who know how to do it. Very often someone will guide you through a trivial process like choosing an option from a menu; then when the crucial information point comes, they ask you to move over and type at lightening-speed on your keyboard, and are then completely unable to explain to you what they did. Installing an Apache web server on a windows machine to run locally is like this; even after you've figured it out and got it working, people will come along to tell you there is something--they can't say what--wrong with the way you've done it and it will destroy the entire internet if you leave it that way; they'll sit with you long enough to break it completely, then shrug and go away. I haven't published my Apache notes yet but I wonder if I'll get hate mail when I do.
view entire entry:
2001_08_27:16: Late Cookies

to see pictures, view entire journal
perl
respond
responses
Testing submission when cookies are enabled AFTER login
view entire entry:
2001_04_19:15: Interview With Farsam

to see pictures, view entire journal
perl
Testing head tags.
view entire entry:
2006_09_05:17: Compartmentalization

to see pictures, view entire journal
perl
respond
responses
Yesterday, while attempting to exercise the virtue of laziness, I determined that making my current module of subroutines available to the object module was viciously circular. I guess that's better than determining that what I had already written was viciously circular. Perl is not often stubborn, and it usually lets me do any inadvisable thing I want to. But this once I was glad that it stubbornly refused to let me do something stupid, as I'm sure that the result would have been a bloody mess. I'll find another way around this encapsulation nonsense, which may require nothing more than copying the subroutines from one module to another. Ha.

Oh, and a tidbit I've been meaning to pass on: To make sure a program doesn't die() when you call a method on an undefined object, just wrap the offending statement in single quotes and precede it with eval, like this:

eval '$object->$method = $value';

where some value of $object might very well be an object that is not (yet) defined. Perl will just skip that statement and move on. Priceless.
view entire entry:
2001-02-07:19:32

to see pictures, view entire journal
perl
This journal program, written by yours truly in perl, has been converted by Tom into the Enlightenment online conference software. It will shortly be converted by me into a sort of message board for interactive fun. Meanwhile, I'm about halfway through a lightweight listserver that will integrate the Enlightenment lists into the site. Perl, like patio rats, is a wonderful and annoying creature.
view entire entry:
2003_08_22:18:0Spam Dies, Tech Lives

to see pictures, view entire journal
perl
respond
responses
Farsam wins the prize for Most Fanciful Use of the Word 'Luddite'. In a phone conversation this week, he accused me of being a Luddite because I coded my own online journal-writing program. I had no idea that the fear of technological change could cause one to write an entirely new program!

But I must admit, the only reason that I'm writing in my journal today is that I am procrastinating. If I weren't making fun of my friends, I'd have to write artificial intelligence code, and, being the Luddite that I am, I needed to find some way to prevent myself from promoting technological change.
view entire entry:
2001-02-25:18:18

to see pictures, view entire journal
perl
I'm really only writing in my journal today because I want to stick search engines in the sidebars. I'm too busy reading and publishing submissions to indulge in my own musings today.
view entire entry:
2001_08_27:16: Lynx Browser Test

to see pictures, view entire journal
perl
respond
responses
Writing this entry to test cookie user with the lynx text browser.
view entire entry:
2008_05_24:16: Why and How

to see pictures, view entire journal
perl
respond
responses
I'm really just writing this entry to re-run my program after a lot of testing of my new RSS feed and left a lot of test files lying around. This will clear up the mess and stop giving people File Not Found errors.
view entire entry:
2000-10-26:07:10

to see pictures, view entire journal
perl
I had to force myself to stop coding the journal and start writing in the journal tonight. It is exhilarating, to be so immersed. I forget, when I don't code for a while, how much I enjoy it, how much better my life is for it. The exercise of any skill or knowledge is pleasant. But the exercise of a long-standing way of being is exquisite and all-possessing. I am new to programming, but I am not new to logic. I first engendered my mother's hatred, at the age of five, by demonstrating logical facility; she actually used the words 'goddamned logic' to berate me for the way I was responding to her. An education in philosophy was inescapable. And earning a living writing code makes perfect sense to me, although it usually surprises people. I don't think most people realize what kind of discipline philosophy is. Of course they don't. They think it's bullshit, because 'philosophy' is what they call it when they're spewing bullshit.
view entire entry:
2015_04_23:11: awakening

to see pictures, view entire journal
perl
respond
responses
Today I debugged and fixed my journaling software, which has been broken for years, probably. That's a good sign. Not only is my brain coming back online, but I am also *remembering* things and exercising skills that I thought I had lost for good.

I want to write. But I can't guarantee that I'll keep using this software. I still like it, but I wrote it 'way back in the year 2000, before "blogging" was even a term, and there were only a few not-very-good options to use. Now, there are lots of great programs to use, even though none of them are like this. And the software is definitely not perfect, which means that I'd have to occasionally stop and debug it. On the one hand, that is disruptive to thinking and writing. But on the other, some bugs, like losing an entire entry, would force me to redraft. And I am trying to improve my writing. Writers I admire say that they always write many drafts. I have a tendancy to blurt out thoughts and hit Submit. I think the result is that my writing is not as clear to others as it seems to me.
view entire entry:
2001_06_20:16: Testing

to see pictures, view entire journal
perl
respond
responses
What's that, a language or something?