Sharing books

I've always enjoyed reading. It's doubly enjoyable when I can share a book with someone else. And it's trebly enjoyable if that person enjoys the story so much they want to pass it on.

Yesterday, one of my coworkers brought back Outlander by Diana Gabaldon. She had stopped by to drop off the book and request the next in the series (yes!). In the process of dropping the book off, her descriptions where enthusiastic enough that her manager requested the loan of the book (yes again!!).

<Big Happy Grin>

Anyway, if you haven't read the series, do yourself a favor and pickup the first in the series. I promise, you won't be disappointed. (Unfortunately, I don't leand my books to strangers - I want them to find their way home.)

P.S. I've only read Outlander, Dragonfly in Amber, and Voyager. I see there are three more to get!

Subversion + Subclipse + Eclipse weirdness

I'm not sure if this is a lack of understanding on my part, or if this is some funky issue with the Subclipse plug-in, or something intrinsic with Subversion. I'm not totally sure of the basic actions to take to replicate it, but...

If I update my Subversion repository outside of Eclipse, when I do a "Synchronize with Repository," I get a whole series of directories that need to be updated. "Fine," I usually figure, "I'll just update and be done with it." It makes sense because I've committed a transaction or two elsewhere, so it'll just bring my workspace up-to-date with the latest revision, right?

Nope!

It doesn't go away. Not with the update, not with the replace with latest from repository. The only "fix" I've found is to delete the project and re-add it.

Not a total show stopper, but it is extremely annoying.

What am I missing? I'm running the 1.1.7 version of Subclipse, which is a development branch. So, that could be it, but I'd think more people than myself would whine about it...

Writin' a compiler...

I've been working on a compiler for a few weeks now - 2 hours or so in the evening, sometimes a whole 4 hours when I stretch myself to midnight. Still have to get up around 6 or 6:30, so that's pushing it...

Anyway, the language is a basic-ish language to use in my embedded and small (read: ancient) computer projects. What I've implemented to date actually works and is using an assembler I had written before with a few touch-ups. I have the basic control statements (for-next, while-do, repeat-until, goto, gosub, return, addition/subtraction, comparison operators, logical operators, along with embedded assembly and minor peephole optimizations).

I haven't added the distinction of various datatypes. I originally planned for byte, short, integer, long, possibly real, and strings. Working standard sizes, that long becomes an 8 byte datatype which is a bit large for an embedded language -- think of 8 bit microcontrollers that may only operate on one byte at a time. Is there a 'standard' data typing for 1, 2, 3, and 4 byte numbers? I'm thinking byte (1), short (2), short integer (3), integer (4). But, I'm afraid that "short integer" is too confusing - since "short" is really a "short integer". Thoughts?

I can just skip it too - but in a constrained memory footprint I may want a 3 byte number with a range to 16 million.