+Tue Feb 6 21:37:03 1996 Per Bothner <bothner@kalessin.cygnus.com>
+
+ * stabsread.c (read_range_type): If !self-subrange and language
+ is Chill, assume a true range. If a true_range is a sub_subrange,
+ use builtin_type_int for index_type.
+
+Tue Feb 6 18:38:51 1996 J.T. Conklin <jtc@slave.cygnus.com>
+
+ * nindy-share/nindy.c (say): Use stdarg.h macros when compiling
+ with an ANSI compiler.
+
Mon Feb 5 18:24:28 1996 Steve Chamberlain <sac@slash.cygnus.com>
From Michael_Snyder@NeXT.COM (Michael Snyder):
return init_type (TYPE_CODE_INT, 1, 0, NULL, objfile);
else if (current_symbol && SYMBOL_LANGUAGE (current_symbol) == language_chill
- && SYMBOL_LINE (current_symbol) > 0)
+ && !self_subrange)
goto handle_true_range;
/* We used to do this only for subrange of self or subrange of int. */
return a real pointer. */
handle_true_range:
- /* At this point I don't have the faintest idea how to deal with
- a self_subrange type; I'm going to assume that this is used
- as an idiom, and that all of them are special cases. So . . . */
if (self_subrange)
- return error_type (pp, objfile);
-
- index_type = *dbx_lookup_type (rangenums);
+ index_type = builtin_type_int;
+ else
+ index_type = *dbx_lookup_type (rangenums);
if (index_type == NULL)
{
/* Does this actually ever happen? Is that why we are worrying