Which is not very useful. I'm trying to find the maximum size of an int on the system to pre-generate a small lookup table to put in a C header file. It does know the size of an int on the system (in bytes), so I could calculate MAX_INT from that. That seems like the kind of kludge that Config.pm was meant to prevent!use Config qw/config_vars/; print config_vars('i_limits'); prints i_limits='define';
Anyone know what the deal is?
If I can't trust Config.pm to work accross systems, is there another hack that is more portable?
TIA,
-jackdied
In reply to Config.pm and i_limits by jackdied
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |