#C file peek c how to#
#C file peek c driver#
#C file peek c Pc#

The layout of a pointer depends heavily on which architecture you are on, theoretically it can consist of anything, with numerous fiuelds to show if the address is in physical or virtual memory, etc., Ok, so what I wanted to say is: In some architectures you get meaningful This is actually no different from PEEK and POKE in the >whether the addresses are absolute or relative to some base or segment >specific is the range of numeric addresses which are meaningful, and >_All_ architectures allow the above constructions. # why shouldn't programming languages do? # # Any language keeps its own misunderstandings # This example cannot be compiled under UNIX, VMS, TOS, MAC-OS and Ptpoke(), which you can call with any type of pointer. Now you got peek() and poke(), which must be called withĪn adress specified by segment and offset. I know, it's a very hard job (and you clearly see BASIC's superiority Return((*which_memory_func(func))(adr, val)) Return(flag ? put_one_byte_into_memory : get_one_byte_from_memory) Static uchar put_one_byte_into_memory(adr, value) Static uchar get_one_byte_from_memory(adr) #define ptpoke(ptr,v) (mem_io((ufcp)ptr, MEM_IO_FUNC_POKE, v) #define ptpeek(ptr) (mem_io((ufcp)ptr, MEM_IO_FUNC_PEEK, 0) #define poke(seg,off,v) (mem_io((ufcp)MK_FP(seg,off), MEM_IO_FUNC_POKE, v) #define peek(seg,off) (mem_io((ufcp)MK_FP(seg,off), MEM_IO_FUNC_PEEK, 0) #define MEM_IO_FUNC_POKE ~MEM_IO_FUNC_PEEK : way to do it? I need to go both ways, esp. How does one do this stuffing? Does anyone know of any other

: type of data (i.e., char, int, etc.), and then stuff the ptr with the seg : statements in C? My guess is that you need to use a far pointer to the

#C file peek c how to#

does anyone know how to do equivalent of BASIC's PEEK & POKE You likely **can** address anywhere you want to! But remember, you purists out there, this likely **IS** On some computers you can do this only if the address is within someĪnnointed range.

#C file peek c Pc#

Where the _far implies you are running a PC in 16 bit mode. The answer is 'if you can do it at all in C, you cast the address toĪ pointer of the proper sort and access that pointer. What it is, and you have no choice about using it. If the address of something on you computer is 13556, that's

#C file peek c driver#

writing to device registers.Īny subroutine written in C for the purpose of being a device driver forĪ machine with memory mapped IO or IO vectors will need them.ĪND FOLKS, PLEASE, don't go blathering about 'portability'. RT11 **system** subroutines (they were not, however, system **calls**,Īs they did not call the OS) called IPEEK and IPOKE, not to mention ISPY.Īnd, of course, the original poster had the correct answer! These callsĪre used or OS sorts of things, e.g. Peek and Poke exist (existed) in far more than just one particular Basic. >nothing that would serve the use it does in Applesoft. >don't believe that there is anything analogous to it in C. >of or put (POKE) a value in to a specific memory address. >PEEK and POKE are used in Applesoft BASIC to look at (PEEK) the contents >describe their task, then this would be lots of help for all the >I am sorry for my ignorance, but what are PEEK and POKE doing? If you Ray Dunn at home | Beaconsfield, Quebec | Phone: (514) 630 3749 Pointers can be created into other segments by using (in MSC) the FP_SEG The address is taken to be relative to the start of the data segment. If you don't, then in small or medium model On the PC you can create an absolute memory address so long as you define

I/O ports can be accessed using the same technique too. Way, and of course if running on hardware that has memory mapped I/O, the There are even architectures in which you can address _registers_ in this Whether the addresses are absolute or relative to some base or segment Specific is the range of numeric addresses which are meaningful, and _All_ architectures allow the above constructions. >printf ('And peek gives us: %d ',*address)