Jump to content

David Heffernan

Members
  • Content Count

    3710
  • Joined

  • Last visited

  • Days Won

    185

Posts posted by David Heffernan


  1. I would have imagined that you'd want some coordination, not everybody having their own copies, all different. Also, git in particular, and dvcs in general are very complex. You sure you want to throw that at your users. But hey, what do I know about your needs. Nothing. 

     

    If you want to use git then go ahead. For instance with libgit2. 

    • Like 1

  2. 1 hour ago, Kas Ob. said:

    Debugger after all should not be altering the debugged application allocated memory without explicit user interaction.

    That's not right. In order to evaluate expressions the debugger needs to execute code in the target process. Which may lead to allocations. 

     

    It's a defect that the IDE / debugger leak such objects, but they can't do their job if they can't execute code and perform allocations in the target process. 

    • Like 2

  3. 35 minutes ago, Clément said:

    If I don't use timers I will have to depend on messages to flush. So I might end up with a lot of "unflushed" log. I would depend on the client to call a "flush logs", that would be wrong.

    No you won't. There are plenty of timer free solutions I would expect. Very hard to give advice without context. And very hard to explain why messages are missing with only a partial extract of code.

     

    Anyway, good luck. 


  4. 5 hours ago, aehimself said:

    Also please note that in Windows several environmental variables requires a logoff-logon for the changes to take affect (like %PATH%).

    Don't think that's true. That's the point of the broadcast message. The shell updates its environment and uses that when creating new processes. 


  5. 3 hours ago, Schokohase said:

    And my point is, you do not need to set the cursor if you have synchron long running code (because the OS will do for you) - so it only make sense to set the cursor when having code running async. 

    This approach is what you take when you hate your users. They can't tell whether or not your program is stuck in a non terminating loop, and the OS asks if you want to terminate the program. So only do this if you want to make your users suffer. 

    • Like 1
    • Thanks 2

  6. Don't change libraries and hope. The library you use is known to work well. There's a defect in your code. Work out what it is. Trial and error never works out.

     

    Provide a minimal yet complete program ideally a console app. Then you can hope for some help. 

    • Like 1
×