SHMBASE

I should know this, so feel free to ridicule me. I noticed in the release notes that SHMBASE was set to 0x10A000000L I may not be the swiftest hex guy, but last I checked L was not used. What does that L do? And if I choose to set SHMBASE to 0x10A000000 does it do something different? For those of you that did not make the conference, you missed a GREAT one. I did not sit in a bad presentation... I had the opportunity to listen and talk to Art K. , Jonathan L. , John Miller, Mark S., Lester K , Mr. D. Priest, Mike (cannot remember last name...spoke Queen's English..gave great SQL), Jacques(sp) R, Jack P. GREAT Info and we all had a nice chat with Jerry Keesee and the gang about Informix stay tuned, I am sure Gary will give you more info about the conference in the Insider (shameless plug). Great Conference, Great people, Great Product....oh and the DB2 weenies were cool too! Thanks for the help! Sam sending to informix-list

Gentsch, Sam wrote: > I noticed in the release notes that SHMBASE was set to 0x10A000000L > > I may not be the swiftest hex guy, but last I checked L was not used. > > What does that L do? And if I choose to set SHMBASE to 0x10A000000 does > it do something different? If it was C source code, it would mean that the value is a long integer rather than a plain integer - which might matter on a 64-bit machine but probably wouldn't. In the ONCONFIG file, it means that the string to number conversion stops at the L (last character, I suppose) but otherwise has no significance. I'm not sure why it's in the documentation; it does no harm, but neither does it do any good. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2005.01 -- http://dbi.perl.org/