search for: outputconstantstr

...are all constants their > strict type could always be derived if needed. Also, it would save > space by eliminating the need to create a proliferating number of char > array types of various lengths. Again, I'm not sure what you're getting at here. Have a look at the function outputConstantStrings in lib/Bytecode/Writer/Writer.cpp. Strings currently occupy the "void" type plane, plane 0 (which is a bit of a hack), but we write out the type slot number (index), then the character data, then a terminating null (0) byte. When the reader reads the constant strings, it reads the...

Dear Chris and Reid: Some other random ideas I've had as I've been sifting through the new bytecode format. Please let me know what you think. 1) ANSI C allows for char to default to unsigned char. This is I guess not how it normally is in GCC. If char defaulted to unsigned char several things would be possible. Single char constants that are defined would be almost always stored

...ir >>strict type could always be derived if needed. Also, it would save space >>by eliminating the need to create a proliferating number of char array >>types of various lengths. > >Again, I'm not sure what you're getting at here. Have a look at the >function outputConstantStrings in lib/Bytecode/Writer/Writer.cpp. Strings >currently occupy the "void" type plane, plane 0 (which is a bit of a >hack), but we write out the type slot number (index), then the character >data, then a terminating null (0) byte. When the reader reads the constant >strin...