[comp.sys.sgi] Edge and 4Sight

karron@KARRON.MED.NYU.EDU (11/14/90)

I was wondering what, if any, plans sgi has for upgrading Edge. It seems
to have an old window system that has not been upgraded to match the
NeWS/4Sight. How will Edge fare with X flavor 4Sight (XSight, CrossSight,??).

It would be nice to cut/paste stuff from jot, wsh into/outfrom edge.

Some new commands to breakpoint on the exit from a subroutine as well
as the current on entry subroutines would be appreciated.

Is there any hope for relative line numbering for subroutines ? I would
like to see a relative line number option for line numbers based on the
subroutine, e.g., 1.1 for the first line of the first subroutine. In this
way .dbxinit code would not have to change as the source file was edited/
evolved. It would make edge functions more robust.

A simple command line for syntax for things like displaying all the
elements of a complex structure, like :

for i in 1 3 5;do print ptr->xxx[i];done;

Currently, printing out disparate nonsequencial elements requires a lot of
typing.

When will C++ be debuggable from edge ?

I must say that edge is vastly improved,
and a vital part of program development.

Dan.
+-----------------------------------------------------------------------------+
| karron@nyu.edu (mail alias that will always find me)                        |
|                                         Dan Karron                          |
| . . . . . . . . . . . . . .             New York University Medical Center  |
| 560 First Avenue           \ \    Pager <1> (212) 397 9330                  |
| New York, New York 10016    \**\        <2> 10896   <3> <your-number-here>  |
| (212) 340 5210               \**\__________________________________________ |
| Please Note : Soon to move to dan@karron.med.nyu.edu 128.122.135.3  (Nov 1 )|
+-----------------------------------------------------------------------------+

bstewart@bnlux0.bnl.gov (Bruce Stewart) (11/16/90)

   We have been very well impressed by the robustness of edge in
working with large, complex, and sometimes less-than-ideally
engineered codes. 
   One feature I would find helpful: a visual interface to
delete breakpoints.