4 ms·
gc.cpp, 37,000 lines of code. And some want to remove Regions from the .net framework!
by cm2187 10y ago
gc.cpp, 37,000 lines of code. And some want to remove Regions from the .net framework!
- matthewwarren 10y agoYeah people always find that file surprising. I think the reason for it being soo large is that the GC is shared across all the .NET versions, so having it in one file has some advantages. See https://github.com/dotnet/coreclr/issues/408 https://github.com/dotnet/coreclr/issues/408 for a discussion on reorganizing it.
- LeanderK 10y agosadly, no. Excerpt from the issue > In #401 @cnblogs-dudu referenced a post explaining that the GC was machine-generated from LISP. Since gc.cpp is not a real source code (just intermediate code), but the lisp code is, should it be more useful to publish the lisp source and the transpiler (Source-to-source compiler) for LISP -> CPP?
- matthewwarren 10y agoIt's my understanding that the LISP -> CPP was only done in the beginning and is no longer carried out. I.e. all recent development is done directly in the .cpp source. There's a reply from a Microsoft employee that seems to confirm this, see https://github.com/dotnet/coreclr/issues/408#issuecomment-78081022 https://github.com/dotnet/coreclr/issues/408#issuecomment-78...
- teh_klev 10y agoHere's a comment by Patrick Dussud on an old blog entry explaining the LISP origins of the GC: https://blogs.msdn.microsoft.com/patrick_dussud/2006/11/21/how-it-all-startedaka-the-birth-of-the-clr/#comment-163 https://blogs.msdn.microsoft.com/patrick_dussud/2006/11/21/h... I thought I knew a thing or two about .NET, having used it since beta days, I had no idea LISP was used to bootstrap the original GC code. Fascinating stuff. I've archived it here just in case: http://archive.is/1qk25 http://archive.is/1qk25 Patrick is also interviewed on Channel9 and he talks about the GC. Not watched it yet: https://channel9.msdn.com/Shows/Going+Deep/Patrick-Dussud-Garbage-Collection-Past-Present-and-Future https://channel9.msdn.com/Shows/Going+Deep/Patrick-Dussud-Ga...
- matthewwarren 10y agoYeah that's a great video, he really knows his stuff!
- deleted 10y ago[deleted]
- UnoriginalGuy 10y agoRegions aren't a .Net Framework feature, they're a language feature. There's absolutely no reason they should be in C# and encourage bad coding practices (like overly long .cs files). Even if you need all your code in a single class, you can shard that class across several .cs files to make organisation and maintainability easier. Regions are just a crutch people use to allow them to create 10K+ line .cs files that will eventually become a maintainability nightmare (as well as making merges/check-ins/finding things more annoying in general). Only region I'll use is the built DEBUG one and I only use that to create: private bool IsDebug() { #if DEBUG return true; #else return false; #endif } Stackoverflow answer for why regions are bad: http://softwareengineering.stackexchange.com/questions/53086/are-regions-an-antipattern-or-code-smell http://softwareengineering.stackexchange.com/questions/53086...
- taco_emoji 10y agoI agree about regions, but `#if` et al are preprocessor directives, not regions. They actually influence how your code is compiled.
- lazyman75 10y agoWell, just because YOU cannot write good code with regions doesn't mean it's a bad feature. It's actually very very useful thing, but as with everything, you have to know when and how to use it.