Monday, January 10, 2011

Testing in Internet Explorer (IE6, IE7, IE8) on Mac OS X

There are some great blog entries on ie6, ie7 and ie8 on mac os x step by step and Install Internet Explorer on OSX using VirtualBox, but they are a bit out of date, so since I can't update those entries, I'm writing my own. But I'm standing on the shoulders of others.

What you'll need
  1. Virtual Box - free download from Oracle
  2. Virtual machine images of Windows with IE - free downloads from Microsoft
  3. A network driver - free download from Redhat

1.  Download and Install Virtual Box (from Oracle).

I installed version 4.0.0, current as of Jan 2011.

2.  Download the Virtual PC disk image (from Microsoft).

For instance, let's start with IE8-on-XPSP3.  You'll need an app to open the self-extracting archive (IE8-on-XPSP3.exe) file that you downloaded.

If you don't have Unarchiver, UnRarX or Zipeg, then download Unarchiver.  Double-click on the TheUnarchiver .zip file and it will extract the application.  Move the The Unarchiver to Applications.

Then find the .exe file and right-click on it and go to Open With -> Other... and scroll down and select The Unarchiver. That will create a folder called IE8-on-XPSP3 and inside will be the the .vhd file that you'll use in Virtual Box and a ReadMe.txt that will say what the login password is for the virtual machine.

3.  Down the Paravirtual (virtio) Driver (from Redhat)

Download the .iso file which you will be able to mount in a Virtual Box machine.

4.  Create a new virtual machine in Virtual Box

Start Virtual Box.  Go to the File menu and click Virtual Media Manager.  Find the .vhd file (from Step 2 above) and drag and drop it into the Virtual Media Manager window.  Click OK.

Click the New button on toolbar in Virtual Box.  Enter a name (i.e. "IE8 on WinXP").  Make sure Operating System is "Microsoft Windows" and Version is "Windows XP" and then click Continue.

Leave Memory at 192MB. Click Continue.

Click "Use existing hard disk" and select the .vhd file name. Click Continue. Click Done.

Important: Before starting the virtual machine, set the Network adapter.  Select the new virtual machine in VirtualBox (click Details tab, if not already selected).  Scroll down to the Network section and click on the word Network.  Click the right arrow next to Advanced and set Adapter Type to "Paravirtualized Network (virtio-net)".  Click OK.

Start the virtual machine by clicking the Start button in the toolbar. Login with the password mentioned in the ReadMe.txt file (step 2 above).

Click Activate Later.  You can't activate until you have the network driver installed.

Click Cancel on all the 'Found New Hardware" dialog boxes that appear.

5.  Install the Guest Additions

This step isn't necessary, but it will make your life easier by making the mouse-handling in the virtual machine natural.

Inside the newly booted virtual machine, press the left Command key to release the mouse and go to the Devices menu (top of Mac screen) and click Install Guest Additions.  This mounts a CD drive in the virtual machine and the autorun on the CD prompts you to install software.  Ignore the warnings about unvalidated software and install everything.  At the end click Reboot later. You can reboot now, but it's faster to install the Network Driver first.

6.  Install the Network Driver.

Press the left Command key again and got to the Devices menu and move to CD/DVD Devices and move right to "Remove disk from virtual drive".  Go back to the Devices menu and move to CD/DVD Devices and move right to "Choose a virtual CD/DVD disk file...". Locate the virtio-win .iso file you downloaded in step 3 above.  Select the filename and click Open.

In the virtual machine, click on the Start menu and then right-click on My Computer and then click on Manage.  Click on Device Manager in the left panel.  In the right panel under Network Adapters right click on Network Controller and click "Update Driver...".

Click radio button for "No, no this time".  Click Next.  Click Next again. Click Okay to the warning about unverified driver.

You should now have a network and can activate Windows.  After activating your virtual machine should be good for 30 days.

You can now reboot your virtual machine.


I recommend not using the Q app to convert the .vhd file to a .vdi file. This will allow you to run multiple virtual machines at the same time, but I believe it violates the EULA for the virtual machine from Microsoft.  See the VPC_EULA.txt file that you downloaded in Step 2 above.

I also recommend against using AntiWPA instead of activating Windows because this also probably violates the EULA.

Wednesday, August 4, 2010

Should consensus affect the Supreme Court?

I received an email from the ACLU today that said, in part:
We must demonstrate that there is a national consensus in support of marriage for same-sex couples. Every step forward will make it harder for the Supreme Court is consistent with the Constitution.
Consensus shouldn't affect the Supreme Court, should it?  The inherent flaw in democracy is that the majority can oppress the minority.  The Constitution is supposed to keep that oppression from happening.

I don't care if 99% of people are against gay marriage or black education or .  The Supreme Court should use the 14th amendment to strike down any law that restricts the privileges of citizens.  A privilege is an entitlement granted by the state.  Marriage licenses are granted by the state and entitle citizens to certain benefits.  Seems pretty clear to me that that's a privilege.

Or is the ACLU just being pragmatic?  In an ideal world, perhaps, Supreme Court justices shouldn't be affected by popular opinion, but they are only human, so they probably are affected.

Thursday, May 6, 2010

Jaclyn: The Jarc Compiler

The Fandle R & D team has been busy writing a compiler for Jarc. Today we have released Jarc 12, which includes Jaclyn, the compiler.  Jaclyn compiles to JVM byte code.  Actually, Jaclyn generates a Jasmin assembler source code file and then calls Jasmin to create a .class file.


  Jarc> (compile "foo.arc")
  Generated: ./foo.class
  Jarc> (iload "foo.class")

Performance Improvements

This had a 5x improvement on the startup time for Jarc. From 2.5 seconds to 0.4 seconds.

The run-time improvement is interesting. Initially the compiled code runs more slowly, but then improves after the first two runs.  I ran the Jarc unit tests 10 times and recorded the time for each run.

This may be partially due to the JIT compiler.  Ignoring the initial runs, the compiled code runs about 1/3 faster.

This should shave a few seconds off the cold-startup time for Fandle on Google App Engine and allow slightly more processing per page hit or task.  Page hits (and tasks) have a 30 second limit on App Engine so applications have to be designed to do their processing in 30 second increments.

Tail Recursion

Jaclyn optimizes tail recursive functions to avoid using unnecessary stack space.  It's not generic tail call elimination, which is not possible in the JVM, but when a method calls itself, the compiler generates a jump to the top of the function instead of invoking the function.  This makes recursion feasible for iteration and avoids StackOverflowError exceptions.


These optimizations are needed to optimize tail calls.  If certain macros (like let) are not optimized then the recursive call winds up in a separate function and can't be optimized.  But by optimizing:

  • afn
  • rfn
  • do
  • let

Jaclyn can optimize many instances of tail recursion.

You can download Jarc 12 from SourceForge and you can also browse the source code.

Thursday, March 11, 2010

Using Jarc with App Engine

I've written a sample Jarc web app for Google App Engine.

Overview of the code


  id Long
  description String
  rating String
  created Date
This uses SML format to define the JDO object to persist in App Engine. The script src/mkjdo.arc converts this into a Java class.


(use 'jtml)

(def /home (req res)
      (title "WineRecord - What wines did I like?")
      (link rel "stylesheet" src "winerecord.css")
      (script src "")
      (script "$(document).ready(function() { $(\"input:text:first\").focus(); });"))
        (with-open db (getPersistenceManager pmf*)
          (form action "/add" method "POST"
              (let wines (execute (newQuery db "select from wine.Wine order by created desc range 0,500"))
                (tr (th "Buy Again?") (th "Wine") (th "Date Added") (th))
                (each wine wines
                  (tr (td wine!description)
                      (td wine!rating)
                      (td wine!created)
                      (td (a href (string "/edit?id=" wine!id) "Edit")))))
              (tr (td (text name "description" size 56))
                  (td (select name "rating"
                              (option "yes")
                              (option "no")
                              (option "maybe")))
                  (td (submit value "Add Wine"))
        (a href "/export" "Export Wines") " "
        (a href "/import" "Import Wines")))))

The above is just an excerpt. You can also view the complete winerecord.arc

No, it doesn't use the standard arc html package. I think it would be difficult to make that work since it would require serializing closures to make them available in multiple web servers.

The jtml package uses SML format which has a direct mapping to XHTML. So the tag names should be familiar to anyone familiar with HTML. The only additions to HTML in jtml are abbreviations for input tags based on the type, for instance you can do:

(text name "name" value "foo")
instead of requiring
(input type "text" name "name" value "foo")
Although the latter works also.

Given my rant about the advantages of saving one token you might wonder why I didn't abbreviate the html tags to within and inch of their lives. Well, in this case, I think leveraging compatibility with HTML is more valuable. And you can create your own macros to abbreviate it however you like. It doesn't have to be part of the Jarc language, unlike the Java access syntax which does have to be part of the language.


Jarc has it's own HttpRequest class which supports lookup using apply, so the code can do:

   ... req!rating ...
Instead of
   ... (getParameterValue req "rating") ...


The JDO class created from src/wine.sml is in package "wine". See build.xml where mkjdo is called (around like 32). The second argument to mkjdo is the Java package name to use. I couldn't get App Engine to work if the JDO object was in the default package.

Features of the JDO Wine class

  • Supports lookup using apply - wine!created
  • Supports sref - (= wine!created ...)
  • Has a constructor that takes a map to init the object - (new wine.Wine (getParameterMap req))
  • Has a putAll method to update the object - (putAll wine (getParameterMap req))
So if the HTML form has the same names as the JDO object it is easy to create or update the JDO object from a form.

Source code and Running App

You can download the entire source from and you can play with the running app at

Wednesday, March 10, 2010

Java access syntax from Jarc - less dots, more filling

Have you ever wondered if the ease of calling C libraries could be responsible for a lot of Python's popularity? C function calls look just like native Python calls.

import george;

You can't tell from the Python code whether the module, george, is written in C or Python. It doesn't matter to the calling program. That's a simple foreign function interface.

Jarc brings this same simple foreign function interface to Arc. Unlike Clojure and JScheme, the syntax for calling a Java method is the same as for calling any Lisp function.

Jarc> (getTime (new java.util.Date))
Jarc> (getTime "foo")
Error: Symbol 'getTime' has no value

Even though there is no function getTime defined, that function can still be called on a Date instance.

Jarc uses dispatch on first arg to figure out how to evaluate the method call. This was suggested by Paul Graham in Arc at 3 Weeks. Although Arc doesn't currently have dispatch on first arg it is ideal for Jarc to access Java methods.

If you've defined classes in Python (or Perl), this may seem intuitive.

class HelloClass:
    def f(self):
        return 'hello world'
That self there is the first argument to the function. Even though you call the function as x.f() what's happening under the covers is that x is passed as the first argument. This same thing is happening under the covers in Perl and C++.


1. You can treat Arc calls and Java calls exactly the same

Polymorphism, anyone? Here's the Jarc macro with-open, which is just like let except that it also calls close on variable. It is slightly more complicated then that because is always calls close even if there is an error. And it ignores any errors that might happen when calling close.

(mac with-open (var init . exprs)
   `(let ,var ,init
      (protect (fn () ,@exprs)
        (fn () (errsafe (close ,var))))))
This is quite handy and ensures that your "stream" gets closed, both when it is an arc type:
(with-open f (outfile "what.ever")
Where Jarc calls the Arc function close, and when the "stream" is a Java object:
(with-open db (java.sql.DriverManager.getConnection ...)
Where Jarc calls the close method on the java.sql.Connection instance.

2. Java objects work with map

No helper function (like memfn in Clojure) is needed to use Java instance methods with map.

(map 'getTime '(list (new java.util.Date)))
Both map and apply accept a symbol (in addition to a function, of course) and interpret that as a Java method call.

3. One less character

And of course, since succinctness is power, saving one whole character is an advantage as well. Clojure requires you to type an additional period.

(.getTime (new java.util.Date))
Astute readers will know that succinctness is defined by the number of nodes in the parse tree. And the Clojure example above still has the same number of nodes as the Jarc version. But the number of nodes is also a proxy for how hard it is to read the code. Our brains have to process the code too. And I think parsing .getTime requires parsing the dot separately. And it's not useful information. Just like in Python, I don't want to be distracted with extra syntax to indicate that this is a Java method call. It's just a function call and should be just as simple.

Thursday, February 25, 2010

Simplified s-expression XML (SML)

Have you ever finished something and released it to the world and then almost immediately afterward realized a way to improve it? Well, that happened with my last blog post. I woke up in the middle of the night and realized that I don't need the damn @ sign in SML.

This will work just fine:
 (tagname attr "value" attr2 "value2"
   (tagname3 "data"))
When parsing the SML if there's a symbol, it must be an attribute name, because the only other things allowed are sublists and strings. That makes the format a lot more readable. I've updated sml.arc to use this new format.

It will also still accept the old format with the @ signs. Might as well keep it backward compatible. I hope I won't wake up in the middle of the night again tonight.

Tuesday, February 23, 2010

Using s-expressions instead of XML

Last time I needed to manipulate a large XML document I remembered Paul Graham's comment in What Made Lisp Different that programs communicating with s-expressions is an idea recently reinvented as XML. I began to wonder if I could just use s-expressions instead of having to deal with XML.

Step 0: Define an s-expression representation for XML.

 (tagname (@ attr "value" attr2 "value2")
   (tagname3 "data"))
If the attributes are optional, then that requires an extra token (@) to distinguish between attributes and the first nested tag.

If the attributes are not optional, then that requires an extra token (nil) when there are no attributes specified.

Most XML documents I've used have more tags without attributes, so I opted for using @.

Since @ can't be a tag name, if the first thing in the list (after the tag name) is a list whose car is @ then it is the XML attributes for that tag. I dubbed this representation SML (S-expression Meta Language).

UPDATE: I came up with a simpler representation.

Step 1: convert XML to s-expressions.
This seems like a job for Perl. It's great at manipulating data formats. So I wrote which works great.

But it seems like a hack because there might be some XML syntax that it doesn't handle. XSLT was designed for transforming XML so it's a good choice for this also. So of course, I did some Googling and found this xml2sexp.xsl, but it's not complete. It can't even convert itself. So I decided to write my own. Yikes! Now I'm back to writing XML, which I was trying to avoid! I can't think of a programming language that is more unpleasant than XML. But it was a chance to learn XSLT, so I wrote xml2sexp.xsl too.

Step 2: Convert SML back to XML.
Now I'm in the Lisp world, so I can use my Lisp of choice, which happens to be Arc at the moment. So I wrote an Arc library, sml.arc, to convert SML back to XML. There's also a function to pretty-print the SML, since the SML created by the conversion from XML is pretty ugly SML.

Adios, XML! I'll never need to deal with you again. I can just use SML whenever I need to work with XML files.