Mercurial > emacs
comparison etc/NEWS @ 37009:cceb6b28e250
*** empty log message ***
author | Gerd Moellmann <gerd@gnu.org> |
---|---|
date | Mon, 26 Mar 2001 16:39:04 +0000 |
parents | 1381d028009c |
children | e5b70de7b794 |
comparison
equal
deleted
inserted
replaced
37008:f4b355161455 | 37009:cceb6b28e250 |
---|---|
1178 incompatibilities will only show in very uncommon circumstances). | 1178 incompatibilities will only show in very uncommon circumstances). |
1179 However, since the impact is uncertain, these changes may be rolled | 1179 However, since the impact is uncertain, these changes may be rolled |
1180 back depending on user feedback. Therefore there's no forward | 1180 back depending on user feedback. Therefore there's no forward |
1181 compatibility guarantee wrt the new features introduced in this | 1181 compatibility guarantee wrt the new features introduced in this |
1182 release. | 1182 release. |
1183 | |
1184 *** The hardcoded switch to "java" style in Java mode is gone. | |
1185 CC Mode used to automatically set the style to "java" when Java mode | |
1186 is entered. This has now been removed since it caused too much | |
1187 confusion. | |
1188 | |
1189 However, to keep backward compatibility to a certain extent, the | |
1190 default value for c-default-style now specifies the "java" style for | |
1191 java-mode, but "gnu" for all other modes (as before). So you won't | |
1192 notice the change if you haven't touched that variable. | |
1193 | |
1194 *** New cleanups, space-before-funcall and compact-empty-funcall. | |
1195 Two new cleanups have been added to c-cleanup-list: | |
1196 | |
1197 space-before-funcall causes a space to be inserted before the opening | |
1198 parenthesis of a function call, which gives the style "foo (bar)". | |
1199 | |
1200 compact-empty-funcall causes any space before a function call opening | |
1201 parenthesis to be removed if there are no arguments to the function. | |
1202 It's typically useful together with space-before-funcall to get the | |
1203 style "foo (bar)" and "foo()". | |
1204 | |
1205 *** Some keywords now automatically trigger reindentation. | |
1206 Keywords like "else", "while", "catch" and "finally" have been made | |
1207 "electric" to make them reindent automatically when they continue an | |
1208 earlier statement. An example: | |
1209 | |
1210 for (i = 0; i < 17; i++) | |
1211 if (a[i]) | |
1212 res += a[i]->offset; | |
1213 else | |
1214 | |
1215 Here, the "else" should be indented like the preceding "if", since it | |
1216 continues that statement. CC Mode will automatically reindent it after | |
1217 the "else" has been typed in full, since it's not until then it's | |
1218 possible to decide whether it's a new statement or a continuation of | |
1219 the preceding "if". | |
1220 | |
1221 CC Mode uses Abbrev mode to achieve this, which is therefore turned on | |
1222 by default. | |
1223 | |
1224 *** M-a and M-e now moves by sentence in multiline strings. | |
1225 Previously these two keys only moved by sentence in comments, which | |
1226 meant that sentence movement didn't work in strings containing | |
1227 documentation or other natural language text. | |
1228 | |
1229 The reason it's only activated in multiline strings (i.e. strings that | |
1230 contain a newline, even when escaped by a '\') is to avoid stopping in | |
1231 the short strings that often reside inside statements. Multiline | |
1232 strings almost always contain text in a natural language, as opposed | |
1233 to other strings that typically contain format specifications, | |
1234 commands, etc. Also, it's not that bothersome that M-a and M-e misses | |
1235 sentences in single line strings, since they're short anyway. | |
1236 | |
1237 *** Support for autodoc comments in Pike mode. | |
1238 Autodoc comments for Pike are used to extract documentation from the | |
1239 source, like Javadoc in Java. Pike mode now recognize this markup in | |
1240 comment prefixes and paragraph starts. | |
1241 | |
1242 *** The comment prefix regexps on c-comment-prefix may be mode specific. | |
1243 When c-comment-prefix is an association list, it specifies the comment | |
1244 line prefix on a per-mode basis, like c-default-style does. This | |
1245 change came about to support the special autodoc comment prefix in | |
1246 Pike mode only. | |
1247 | |
1248 *** Better handling of syntactic errors. | |
1249 The recovery after unbalanced parens earlier in the buffer has been | |
1250 improved; CC Mode now reports them by dinging and giving a message | |
1251 stating the offending line, but still recovers and indent the | |
1252 following lines in a sane way (most of the time). An "else" with no | |
1253 matching "if" is handled similarly. If an error is discovered while | |
1254 indenting a region, the whole region is still indented and the error | |
1255 is reported afterwards. | |
1256 | |
1257 *** Lineup functions may now return absolute columns. | |
1258 A lineup function can give an absolute column to indent the line to by | |
1259 returning a vector with the desired column as the first element. | |
1260 | |
1261 *** More robust and warning-free byte compilation. | |
1262 Although this is strictly not a user visible change (well, depending | |
1263 on the view of a user), it's still worth mentioning that CC Mode now | |
1264 can be compiled in the standard ways without causing trouble. Some | |
1265 code have also been moved between the subpackages to enhance the | |
1266 modularity somewhat. Thanks to Martin Buchholz for doing the | |
1267 groundwork. | |
1183 | 1268 |
1184 *** c-style-variables-are-local-p now defaults to t. | 1269 *** c-style-variables-are-local-p now defaults to t. |
1185 This is an incompatible change that has been made to make the behavior | 1270 This is an incompatible change that has been made to make the behavior |
1186 of the style system wrt global variable settings less confusing for | 1271 of the style system wrt global variable settings less confusing for |
1187 non-advanced users. If you know what this variable does you might | 1272 non-advanced users. If you know what this variable does you might |