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,d534ff88bae65c48,start
X-Google-Attributes: gid103376,public
From: Stephen Leake <Stephen.Leake@gsfc.nasa.gov>
Subject: hunting snarks
Date: 1999/12/14
Message-ID: <uzovdbc46.fsf@gsfc.nasa.gov>#1/1
X-Deja-AN: 560634862
Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA
Newsgroups: comp.lang.ada
Date: 1999-12-14T00:00:00+00:00
List-Id: <comp.lang.ada>

I wasted a couple of hours this past weekend due to what I propose we
call "the snark effect". The snark effect occurs when you change the
profile of a dispatching operation, and forget to change one of the
overriding operations on a derived type; the overriding operation
"silently vanishes away".

Connoisseurs of Lewis Carrol will protest that this should be the
"boojum snark effect", but that's too many words.

Anyway, this problem has been mentioned here before. I'm considering
hacking into GNAT to provide a fix, probably in the form of a pragma
Overrides. But first, I'd like to check if anyone else is working on a
solution, or has a proposal for a syntax for a solution.

Anyone?

-- Stephe