7 ms·
I said "perhaps" because while it might be misleading in the sense that this isn't some discovered memory leak in the C# language, it is an example of how progr
by boucher 19y ago
I said "perhaps" because while it might be misleading in the sense that this isn't some discovered memory leak in the C# language, it is an example of how programming mistakes in garbage collected languages can still lead to "memory leaks". To be more specific, memory that you intended to be freed and made available was not. You can argue about the semantics, but I think the intent of saying memory leak is clear here in the context of the article.
- wyday 19y agoI wasn't arguing about the term "memory leak", but the misleading title's implication that it's a design flaw in the C# specification (or, for that matter, Microsoft's or Mono's implementation). It's not. It's a memory leak due to the programmers error.
- boucher 19y agoAnd I wasn't arguing that the title wasn't misleading. Just that while it may be slightly misleading, the article itself clearly puts it in context. perhaps: "used to express reluctant or qualified agreement or acceptance."