From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,fd6a7b18ad586b7f,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-07-08 19:07:20 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newshub2.home.com!news.home.com!news1.rdc1.mi.home.com.POSTED!not-for-mail From: "McDoobie" Subject: Working with very large numbers. Newsgroups: comp.lang.ada Organization: The Caffinated Corps. User-Agent: Pan/0.8.1beta4 (Unix) X-No-Productlinks: Yes Message-ID: Date: Mon, 09 Jul 2001 02:07:19 GMT NNTP-Posting-Host: 24.0.109.49 X-Complaints-To: abuse@home.net X-Trace: news1.rdc1.mi.home.com 994644439 24.0.109.49 (Sun, 08 Jul 2001 19:07:19 PDT) NNTP-Posting-Date: Sun, 08 Jul 2001 19:07:19 PDT Xref: archiver1.google.com comp.lang.ada:9652 Date: 2001-07-09T02:07:19+00:00 List-Id: Alright...I know about long_integers and long_long_integers and all that. What I'm trying to figure out is how do I work with numbers in which the standard supplied types are just too small? Specifically, how do I allocate storage dynamically based upon the size of the integer entered? I was thinking about using something along the lines of ... type big_ass_num; type biggie_ptr is access big_ass_num; type big_ass_num is (s , (len)'value); Big_Kahuna: biggie_ptr'(big_ass_num'Range(<>)); Little_Kahuna: biggie_ptr'(big_ass_num'Range( Big_Kahuna > ... (<>)); Or some crazy crap along those lines. Anyways, as you can tell, I havent quite got the gist of it yet. Any help would be appreciated. McDoobie chris@dont.spam.me