Re: Multiple procedures in the same adb file?

[John Smith <yoursurrogategod@gmail.com>]

37,000,000 lines of code?  What was the application supposed to do?  Simulate planet earth?

On Sunday, January 11, 2015 at 4:02:21 PM UTC-5, Robert A Duff wrote:
> John Smith <you...@gmail.com> writes:
> 
> > Thanks, that was really helpful.
> 
> You're welcome.
> 
> >...  I got it to work by making the appropriate *.ads and *.adb files.
> >I also had it working as a nested function.
> >
> > It seems a tad tedious at first, ...
> 
> Yes, it's a nuisance for small programs.  But for large programs,
> one compilation_unit per file with a file-naming convention is
> really the only sensible way.  But I must admit, I'd prefer GNAT
> to be able to handle multiple compilation_units per file without
> so much horsing around.
> 
> That's partly because when I'm debugging GNAT, I'm often working
> with very small test programs.  If a customer hands me a huge
> program that causes GNAT to crash, I'll usually try debugging
> it directly first, but if I can't figure it out quickly that way,
> I'll try making a small cut-down test that crashes in the same way.
> If the small test case contains 30 lines of code in 5 files,
> that's just a nuisance.  So I use gnatchop.
> 
> Most bug reports are already small.  The biggest one I had to
> deal with at AdaCore was about 37,000,000 lines of code.
> 
> > ...but it does make sense.  Heck, even C/C++ recommends a similar
> > approach.  You want to separate the declaration from the
> > implementation.
> 
> Right, same idea.
> 
> - Bob