summaryrefslogtreecommitdiff
path: root/JOURNAL
diff options
context:
space:
mode:
authorMatthias Benkard <code@mail.matthias.benkard.de>2007-10-04 17:32:41 +0200
committerMatthias Benkard <code@mail.matthias.benkard.de>2007-10-04 17:32:41 +0200
commit9a3ec83a6db3ca95be8a4bf11620f93bfa348a4b (patch)
tree6fa6a775c7c2bf974ccf5e6546f8bdee54c0e759 /JOURNAL
parentb8764bfc2acf5f569b864a8b30175d2285b529d7 (diff)
Make type handling work on the GNU runtime again.
darcs-hash:fc311f5f95252858c3d57007d43f5eb327db7cd6
Diffstat (limited to 'JOURNAL')
-rw-r--r--JOURNAL17
1 files changed, 17 insertions, 0 deletions
diff --git a/JOURNAL b/JOURNAL
index a4741ee..77f7021 100644
--- a/JOURNAL
+++ b/JOURNAL
@@ -1,5 +1,22 @@
-*- mode: muse -*-
+* 2007-10-04, 17:27:02 CEST
+
+** `char' Does Actually Indicate a Char, Sometimes
+
+The latest changes made the test cases fail on GNUstep/x86, which either
+means that the PyObjC code is wrong, or the GNU runtime has very weird
+calling conventions that use ints as wrappers for chars or something.
+Anyway, I have reverted the changes for GNUstep and left them in place
+for Mac OS X (but note that I left the PyObjC code as it is, which means
+that libffi is still directed to treats chars as ints). As a result,
+both NeXT/PowerPC and GNUstep/x86 work for now, but I'm uncertain about
+the status of other architectures as well as calling methods with chars
+and shorts as arguments, which I've got no test cases for. I'm not
+confident that either GNUstep/PowerPC/SPARC/whatever or NeXT/x86 work
+the way my code expects them to.
+
+
* 2007-10-04, 16:52:32 CEST
** `char' Does Not Indicate a Char, Continued