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,ad84be6ce1cbae14,start X-Google-Attributes: gid103376,public From: "Rainer Aigner Tel. XXXX" Subject: Take controll of the assignment operator Date: 2000/04/11 Message-ID: <38F2FF84.C44AC279@newtec.de>#1/1 X-Deja-AN: 609587918 Content-Transfer-Encoding: 7bit Organization: Daimler-Benz Aerospace X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 2000-04-11T00:00:00+00:00 List-Id: Hello , !Please excuse by bad english! I'm a new one in this news group, and a beginner in programming ADA95. Right now I have to write some TSAP's in RISC Class 1. The question I have I just an idea I had, and I just didn't find a solution for over 2 weeks or so. Here's the problem: I define some types: type unsigned_byte is mod 2**8; for unsigned_byte'size use 8; type unsigned_word is mod 2**16; for unsigned_word'size use 16; type unsigned_longword is mod 2**32; for unsigned_longword'size use 32; Up to here everythings fine. Now, my question: How can I make sure that the compiler uses the right assembler for load and store operations? My target is a PowerPC and has for each type it's own assembler statement, and I got to sure (RISC Class 1) that a particular assembler statment is used. My first intention was to overload the assignment operator for each type to get controll over the load/store operations. But after several hours I kicked this idea, because the assignment operator is the only one which can not be overloaded. The workaround right now are sperate load/store procedures. But that's not what I wanted. Okay You can live with it but.. So if anybody has an idea, I would be very thankfull. cu Rainer Aigner mailto: aigner@newtec.de