emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] /srv/bzr/emacs/trunk r111725: Remove obsolete references t


From: Paul Eggert
Subject: [Emacs-diffs] /srv/bzr/emacs/trunk r111725: Remove obsolete references to VAX in comments.
Date: Sun, 10 Feb 2013 16:35:37 -0800
User-agent: Bazaar (2.5.0)

------------------------------------------------------------
revno: 111725
committer: Paul Eggert <address@hidden>
branch nick: trunk
timestamp: Sun 2013-02-10 16:35:37 -0800
message:
  Remove obsolete references to VAX in comments.
modified:
  etc/PROBLEMS
  lisp/net/ange-ftp.el
  src/cm.c
  src/fileio.c
=== modified file 'etc/PROBLEMS'
--- a/etc/PROBLEMS      2013-01-01 09:11:05 +0000
+++ b/etc/PROBLEMS      2013-02-11 00:35:37 +0000
@@ -3198,39 +3198,6 @@
 
 This seems to be due to a GCC bug; it is fixed in GCC 2.8.1.
 
-** Vax C compiler bugs affecting Emacs.
-
-You may get one of these problems compiling Emacs:
-
-   foo.c line nnn: compiler error: no table entry for op STASG
-   foo.c: fatal error in /lib/ccom
-
-These are due to bugs in the C compiler; the code is valid C.
-Unfortunately, the bugs are unpredictable: the same construct
-may compile properly or trigger one of these bugs, depending
-on what else is in the source file being compiled.  Even changes
-in header files that should not affect the file being compiled
-can affect whether the bug happens.  In addition, sometimes files
-that compile correctly on one machine get this bug on another machine.
-
-As a result, it is hard for me to make sure this bug will not affect
-you.  I have attempted to find and alter these constructs, but more
-can always appear.  However, I can tell you how to deal with it if it
-should happen.  The bug comes from having an indexed reference to an
-array of Lisp_Objects, as an argument in a function call:
-  Lisp_Object *args;
-  ...
-   ... foo (5, args[i], ...)...
-putting the argument into a temporary variable first, as in
-  Lisp_Object *args;
-  Lisp_Object tem;
-  ...
-   tem = args[i];
-   ... foo (r, tem, ...)...
-causes the problem to go away.
-The `contents' field of a Lisp vector is an array of Lisp_Objects,
-so you may see the problem happening with indexed references to that.
-
 
 This file is part of GNU Emacs.
 

=== modified file 'lisp/net/ange-ftp.el'
--- a/lisp/net/ange-ftp.el      2013-02-09 12:52:01 +0000
+++ b/lisp/net/ange-ftp.el      2013-02-11 00:35:37 +0000
@@ -5133,7 +5133,7 @@
        (forward-line 1))
       ;; Would like to look for a "Total" line, or a "Directory" line to
       ;; make sure that the listing isn't complete garbage before putting
-      ;; in "." and "..", but we can't even count on all VAX's giving us
+      ;; in "." and "..", but we can't count on VMS giving us
       ;; either of these.
       (puthash "." t tbl)
       (puthash ".." t tbl))

=== modified file 'src/cm.c'
--- a/src/cm.c  2013-01-01 09:11:05 +0000
+++ b/src/cm.c  2013-02-11 00:35:37 +0000
@@ -28,8 +28,7 @@
 #include "termchar.h"
 #include "tparam.h"
 
-#define        BIG     9999            /* 9999 good on VAXen.  For 16 bit 
machines
-                                  use about 2000.... */
+#define        BIG     9999            /* Good on 32-bit hosts.  */
 
 int cost;              /* sums up costs */
 

=== modified file 'src/fileio.c'
--- a/src/fileio.c      2013-02-10 08:26:56 +0000
+++ b/src/fileio.c      2013-02-11 00:35:37 +0000
@@ -133,9 +133,6 @@
    is added here.  */
 static Lisp_Object Vwrite_region_annotation_buffers;
 
-#ifdef HAVE_FSYNC
-#endif
-
 static Lisp_Object Qdelete_by_moving_to_trash;
 
 /* Lisp function for moving files to trash.  */
@@ -4965,7 +4962,7 @@
   immediate_quit = 0;
 
 #ifdef HAVE_FSYNC
-  /* Note fsync appears to change the modtime on BSD4.2 (both vax and sun).
+  /* fsync appears to change the modtime on BSD4.2.
      Disk full in NFS may be reported here.  */
   /* mib says that closing the file will try to write as fast as NFS can do
      it, and that means the fsync here is not crucial for autosave files.  */


reply via email to

[Prev in Thread] Current Thread [Next in Thread]