Fix value_literal_complex comment
Christian pointed out that the value_literal_complex was still a bit weird; this patch rewrites it and moves it to value.h. gdb/ChangeLog 2020-04-01 Tom Tromey <tom@tromey.com> * value.h (value_literal_complex): Add comment. * valops.c (value_literal_complex): Refer to value.h.
This commit is contained in:
parent
3638a098a2
commit
6b4a335bf7
|
@ -1,3 +1,8 @@
|
|||
2020-04-01 Tom Tromey <tom@tromey.com>
|
||||
|
||||
* value.h (value_literal_complex): Add comment.
|
||||
* valops.c (value_literal_complex): Refer to value.h.
|
||||
|
||||
2020-04-01 Tom Tromey <tom@tromey.com>
|
||||
|
||||
* c-exp.y (FLOAT_KEYWORD, COMPLEX): New tokens.
|
||||
|
|
|
@ -3854,12 +3854,10 @@ value_slice (struct value *array, int lowbound, int length)
|
|||
return slice;
|
||||
}
|
||||
|
||||
/* Create a value for a FORTRAN complex number. Currently most of the
|
||||
time values are coerced to COMPLEX*16 (i.e. a complex number
|
||||
composed of 2 doubles. */
|
||||
/* See value.h. */
|
||||
|
||||
struct value *
|
||||
value_literal_complex (struct value *arg1,
|
||||
value_literal_complex (struct value *arg1,
|
||||
struct value *arg2,
|
||||
struct type *type)
|
||||
{
|
||||
|
|
|
@ -1138,6 +1138,10 @@ extern struct value *varying_to_slice (struct value *);
|
|||
|
||||
extern struct value *value_slice (struct value *, int, int);
|
||||
|
||||
/* Create a complex number. The type is the complex type; the values
|
||||
are cast to the underlying scalar type before the complex number is
|
||||
created. */
|
||||
|
||||
extern struct value *value_literal_complex (struct value *, struct value *,
|
||||
struct type *);
|
||||
|
||||
|
|
Loading…
Reference in New Issue