Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #68512
| From | Ian Collins <ian-news@hotmail.com> |
|---|---|
| Newsgroups | comp.lang.c++ |
| Subject | Re: Visual Studio 2019 Edit-and-continue |
| Date | 2019-09-19 08:17 +1200 |
| Message-ID | <gufhm6FldqU1@mid.individual.net> (permalink) |
| References | <qlre3f$5m3$1@dont-email.me> <aedef0d1-75b7-4028-93c2-09cae4c9c3f7@googlegroups.com> <qlt6g8$npp$1@dont-email.me> <0b6d46df-499d-47c4-9c08-f73b42191d83@googlegroups.com> |
On 19/09/2019 03:24, Öö Tiib wrote: > On Wednesday, 18 September 2019 15:04:36 UTC+3, Rick C. Hodgin wrote: >> On 9/18/2019 3:43 AM, Öö Tiib wrote: >>> On Tuesday, 17 September 2019 23:02:03 UTC+3, Rick C. Hodgin wrote: >>>> [If anyone knows a better place to post this question, please let me >>>> know and I'll take it there.] >>> >>> I don't think you will get good (or even much different) answer to that >>> question from anywhere. It is generally always same. >>> Q: Why a software product does not allow certain scenario of usage? >>> A: Because support for that scenario hasn't been implemented. >>> Q: Why it hasn't been implemented? >>> A: Because implementers put their effort into other features. >>> Q: Why? >>> A: Because the stakeholders prioritized other features as being >>> of higher importance. >>> Q: Why? >>> A: Because they wanted to. >> >> >> If that's all it is I understand. If there's something I don't know >> about why it needs to remain attached, that's the thing I'd like to >> learn. From writing my own OS, debugger, and tools, I don't see a >> reason other than just a decision to keep the in-memory-app aligned >> with the on-disk-app, so they aren't out of sync. Seems to be a >> policy decision rather than a technical one. And that's fine. I'd >> just like to learn if it's otherwise (if it's otherwise). > > The whole edit and continue is quite rare feature in compiled > languages. Is it because of policy decisions or technical issues? > I see it as technically challenging feature. Indeed. I can also see a it as a good way to make malicious changes to a binary, so having to leave the debugger attached could be seen as a security feature. -- Ian.
Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Visual Studio 2019 Edit-and-continue "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-09-17 16:01 -0400
Re: Visual Studio 2019 Edit-and-continue Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2019-09-17 21:41 +0100
Re: Visual Studio 2019 Edit-and-continue Öö Tiib <ootiib@hot.ee> - 2019-09-18 00:43 -0700
Re: Visual Studio 2019 Edit-and-continue David Brown <david.brown@hesbynett.no> - 2019-09-18 10:18 +0200
Re: Visual Studio 2019 Edit-and-continue Öö Tiib <ootiib@hot.ee> - 2019-09-18 07:54 -0700
Re: Visual Studio 2019 Edit-and-continue "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-09-18 11:30 -0400
Re: Visual Studio 2019 Edit-and-continue Öö Tiib <ootiib@hot.ee> - 2019-09-18 23:50 -0700
Re: Visual Studio 2019 Edit-and-continue "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-09-19 08:31 -0400
Re: Visual Studio 2019 Edit-and-continue "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-09-18 08:04 -0400
Re: Visual Studio 2019 Edit-and-continue Öö Tiib <ootiib@hot.ee> - 2019-09-18 08:24 -0700
Re: Visual Studio 2019 Edit-and-continue "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-09-18 11:30 -0400
Re: Visual Studio 2019 Edit-and-continue "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-09-18 11:33 -0400
Re: Visual Studio 2019 Edit-and-continue Ian Collins <ian-news@hotmail.com> - 2019-09-19 08:17 +1200
Re: Visual Studio 2019 Edit-and-continue "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2019-09-18 16:29 -0400
Re: Visual Studio 2019 Edit-and-continue Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2019-09-18 22:27 +0100
csiph-web