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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,fcf8ea94b94d6941 X-Google-Attributes: gid103376,public From: Stephen Leake Subject: Re: Modular type. What is it and why? Date: 1999/04/07 Message-ID: #1/1 X-Deja-AN: 463740033 References: <7ean3c$79m$1@eol.dd.chalmers.se> <7eb2iq$jc3@hobbes.crc.com> <7ede2p$pd1$1@its.hooked.net> <370A4B3A.5EDB3B37@pwfl.com> <7edk6p$1j7$1@its.hooked.net> <7eftdm$7rn$1@its.hooked.net> Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA Newsgroups: comp.lang.ada Date: 1999-04-07T00:00:00+00:00 List-Id: "Mike Silva" writes: > Actually, the more I thought about it the more the static limitation on > modular types makes my idea worthless. Even if NUM_ELEMENTS is static for > each menu, I'd want the same routine to handle multiple menus, each with a > different NUM_ELEMENTS. Oh well... That's what generics are for. Unless the number of elements in a given menu is dynamic. -- Stephe