Download out-of-order (dropbox)

posted Mar 4, 2017, 4:02 AM by Hans-Peter Suter

As per 2017-03-15 dropbox removes public folders. Our download was based on such a public folder.

Considering that xlsReadWrite[Pro] is 32bit-legacy and likely only used by few people now, we don't setup a new download method. In case you need a file, please ask by email.

R3.x compatible package version released (15.3.2014)

posted Mar 15, 2014, 3:47 PM by Hans-Peter Suter   [ updated Mar 15, 2014, 3:57 PM ]

While xlsReadWrite[Pro] should be considered as deprecated we have just released xlsReadWrite v1.5.5 and xlsReadWritePro v1.6.5  which support again the latest R version. The check has been executed with 32-bit R3.0.3 on Windows 8.1 and all our (many) R unit tests did run successfully.

But why is it deprecated when it runs well?

There are three reasons: 1. it only runs with the 32-bit R version, 2. there is neither crossplatform nor xlsx support and 3. we no longer maintain a Delphi toolchain**

**to be honest, this new package versions were not compiled but we directly modified the assembler code to make it R3.x compatible (different argument checking in .External register call, iirc). Because of this 'hack' we didn't like the thought to make it officially available (but people kept asking)

Future development (18.7.2012)

posted Jul 18, 2012, 3:48 AM by Hans-Peter Suter   [ updated Jul 18, 2012, 3:48 AM ]

An xlsReadWrite[Pro] successor (called xlReadWrite[Pro]) should have come in early 2012 but I got distracted by other hobby-projects and considering that there are alternatives (e.g. XLConnect) I was not ready to release my 'half-baked' attempt.

I cannot currently commit to a new firm release date. Things I was working on and things I attempt to support with the next version include:
  • xlsx file format (in addition to .xls/BIFF8 format)
  • support 64 bit
  • support Mac OSX
  • (support Linux (Debian), demands using FreePascal instead of Delphi)
  • (pro version) much more capable API: formatting, merging, S3 objects (in addition), ...
Finishing all this takes time and 'release early and often' is, imho, not a good idea here.

1-3 of 3