Posts filed under 'Cross Platform'

Code Crusader 5.1

Code Crusader 5.1 is finally finished. In case you haven’t noticed, the release schedule is a bit faster than it has been in recent years. :)

You can read about the changes here. One noteworthy improvement is that it now runs on Cygwin!

This release is free for those who have purchased version 5.0. Simply log in to your account on the Downloads page.

Add comment June 11th, 2006

Cygwin

I finally got Code Crusader and Code Medic to run on Cygwin! I’ll be posting the binaries as soon as Code Crusader 5.1.0 is finished.

Add comment June 6th, 2006

Cygwin

I just updated my WinXP laptop to the latest Cygwin and discovered the following issues:

  1. mkdtemp() is missing from the system libraries.
  2. seekg() and seekoff() require long long instead of long
  3. JOutPipeStream generates additional link errors, but this class is scheduled for replacement anyway.

If anybody has any information about how to cope with this, please let us know!

Add comment February 11th, 2006

Porting JX

The good news, in case you hadn’t noticed, is that our software now runs on both Mac OS and Cygwin — at least, out latest beta does. :)

Porting our software to Windows 2K/XP has been stalled for a few months now, but the good news is that I recently made a bit more progress by eliminating most of the uses of JInPipeStream. This particular class was originally a good idea, but since it is based on a GNU extension to the C++ stream library which never caught on, it now has to go. I’m replacing it with functions in jStreamUtil.h that operate directly on a file descriptor. Of course, this means that we lose the convenience of the stream in operator (>>), but that seems to be a small price to pay for cross-platform compatibility.

The same fate awaits JOutPipeStream.

On a similar note, since strstream is deprecated, almost all references to it have been replaced with stringstream, and jStrStreamUtil.h is now gone. Personally, I dislike the descision to deprecate strstream, because stringstream always makes copies of the data, and this is a disaster in certain cases where efficiency is critical — though I suppose some would claim that the entire C++ stream library should be avoided when efficiency matters! :???:

If anybody has any good news about stringstream colluding with string to avoid copying data, please let me know!

Add comment November 29th, 2005


Calendar

July 2008
M T W T F S S
« Jun    
 123456
78910111213
14151617181920
21222324252627
28293031  

Posts by Month

Posts by Category