{ |one, step, back| } 175 to 180 of 180 articles WikiSyndicate: full/short

Polyglot Polymorphism   23 May 03
[ print link all ]
In an email converversion on the CLUG (www.clug.org) mailing list some time ago, we got on the topic of doing Object Oriented program (with runtime polymorphism) in a non-OO language like C. What would it take, what would the code look like and is it worth it?

Using the standard shapes example, I posted some code in C showing how to do runtime polymorphism using pointers to functions. I also include C++ and Java examples. Then everybody got in the act and we ended up with this (onestepback.org/articles/poly).

Some of the source files are missing, and I’ll replace them when I can. In the meantime, enjoy.

Welcome Visiters   23 May 03
[ print link all ]
Welcome to the Weirich on the Web, OneStepBack web pages. This is the new version of what used to be called the Weirich on the Web pages (w3.one.net/~jweirich). The format has changed a bit. We are now using a blog-like front page. But most of the same material is here (or will eventually migrate here … give me time!).

Feel free to provide feedback at jweirich@one.net.

Some Rights Reserved   23 May 03
[ print link all ]
Some Rights Reserved Creative Commons

Most content on this site is covered by a Creative Content License. Materials not covered by this license will be explicitly noted (for example, most of the code is offered under one of the Open Source/Free Software licenses).

This Creative Commons license essentially says that you have permission to use the material covered by the license for non-commericial purposes as long as you attribute it to the author (that would be me). Click on the Creative Commons graphic for all of the details.

Of course, this only applies to the material written by me (Jim Weirich). Material written by others will be covered by their own copyrights.

Check out the Creative Commons web site. They have a number of different licences available, and they do a good job of explaining them. There may be a license there that suites your needs.

UML Coop WIKI is Now Available   17 May 03
[ print link all ]
A Wiki devoted to UML Coop questions and answers is availbe at jimweirich.umlcoop.net/cgi-bin/umlwiki.pl. UML Coop members are invited to use it.

What Do You Need?   17 May 03
[ print link all ]
So, you are facing a freshly installed copy of Linux. It has the basics, but nothing else. What do you install first?

I can answer that question because I just did it for the UML system you see here.

Here’s what I loaded …

  • I have download most of my brain into Emacs macros, so working without emacs for any length of time is not acceptable. Fortunately, a quick ‘apt-get install emacs21’ and a working emacs system becomes available.
  • After loading emacs, I grabbed the .emacs file (and all of its supporting libraries) from my desktop system.
  • My overall plan for this UML system is to use it as my web host. That means that apache is required. Grabbing apache with apt-get was simple.
  • I plan to base my web site around a Ruby based blogging package called Rublog. That means Ruby will be needed. Since I tend to track the latest version of Ruby a little more closely than Debian does, I normally install Ruby by hand from source. Fortunately, installing Ruby is trivial. I just downloaded the source (from www.ruby-lang.org), and did the standard configure/make/make install commands.
  • Next I needed the Rublog software. I had been playing with Rublog on my laptop, so I had the configuration pretty well decided by that point. I just copied the laptop setup to the UML system.
  • Finally, Rublog needs RDoc to render any RDoc postings. A quick visit to the Ruby Application Archive to grab RDoc and I was good to go.

And that completed my first phase of setups. I had to do a little reading on setting up iptables and a bit of configuration with apache. The result is what you see here.

So, what packages do you need to work with.

One Step Back   17 May 03
[ print link all ]

… from the Edge

 

Formatted: 04-Jul-08 14:30
Feedback: jim@weirichhouse.org