| delorie.com/archives/browse.cgi | search |
| From: | Thomas Demmer <demmer AT LSTM DOT Ruhr-UNI-Bochum DOT De> |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: hexidecimal confusion |
| Date: | Wed, 17 Dec 1997 07:43:45 +0100 |
| Organization: | Lehrstuhl fuer Stroemungsmechanik |
| Lines: | 28 |
| Message-ID: | <349774A1.A36AD372@LSTM.Ruhr-UNI-Bochum.De> |
| References: | <677kii$qmv$1 AT newsfep4 DOT sprintmail DOT com> |
| NNTP-Posting-Host: | bvb.lstm.ruhr-uni-bochum.de |
| Mime-Version: | 1.0 |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Ionicis wrote: > > Is there a difference between 16h and 0x16? Can you use 16h instead of > 0x16 for things such as interrupt specifiers (int86(16h, ®s, > ®s))? Or must you use 0x16? Is there a difference between the first > form and the latter form (C-wise, not value-wise)? Some clarification > on this would be greatly appreciated. > > "Ionicis" The first form is illegal, the second one is fine. 16h is sometimes used in documentations and printed texts to indicate a hex number. 0x16 is what the C compiler understands. In PASCAL you would say $16. -- Ciao Tom ************************************************************* * Thomas Demmer * * Lehrstuhl fuer Stroemungsmechanik * * Ruhr-Uni-Bochum * * Universitaetsstr. 150 * * D-44780 Bochum * * Tel: +49 234 700 6434 * * Fax: +49 234 709 4162 * * http://www.lstm.ruhr-uni-bochum.de/~demmer * *************************************************************
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |