Who am I?
Konstantine Voytenko
BluSPAN project coordinator
Fishnest Ltd.
bluspan@gmail.com
Calendar
Recently...
- Symbian, Descriptors and Unicode
- PAN service advertise
- Lost in the dark
- Reset S60-3rd emulator defaults
- Attempt to create a CSY module
- Serial protocol modules
- Symbian Networking interface
- Carbide code bookmarks
- Accomplish SSL connection from S60v3
- Insert Multiselection list into GUI
- Get project from CVS to Carbide C++
- Switching Avkon Views
- Code implementation for GUI
- Assembling GUI set reflecting future BluSPAN functionality
- Bluetooth Driver for S60 SDK
- Difference between the pointers in Carbide c++ and C++
- BlueZ port using P.I.P.S. environment
- Obtaining Carbide license
- Port of PAND (BlueZ) system
- The Battle for BlueZ
Categories
Open Source Bluetooth PAN's Forum Nokia Blog
Difference between the pointers in Carbide c++ and C++
Carbider | 17 October, 2007 16:11
One more difference between Carbide C++ and standard C++ that I found while porting is pointers maintaining.
If you have a pointer 'p'
void *p = other_pointer;
in C you can sum it up with integer value to walk through memory:
p += sizeof(uint8_t);
That is frequently used in BlueZ libraries.
But Carbide doesn't allow such manipulation motivating with:
"illegal operands 'void *' + 'unsigned int'"
That is because Carbide is more strict with types than C is.
So to move through memory I need that pointer 'p' would be a pointer to specific data type, not ‘void’.
I decided, 'p' should be a pointer to 'uint8_t' because it is used as type’s length to determine data’s displacement step.
So the final declaration looks like this:
uint8_t *p;;
p += sizeof(uint8_t);
Symbian C++ |
Permalink |
Comments (9) |
Trackbacks (0)
