Source Files

• portions of tclObj.c

Public Routines

• Tcl_NewBooleanObj
• Tcl_DbNewBooleanObj
• Tcl_SetBooleanObj
• Tcl_GetBooleanFromObj
• Tcl_NewDoubleObj
• Tcl_DbNewDoubleObj
• Tcl_SetDoubleObj
• Tcl_GetDoubleFromObj
• Tcl_NewIntObj
• Tcl_SetIntObj
• Tcl_GetIntFromObj
• Tcl_NewLongObj
• Tcl_DbNewLongObj
• Tcl_SetLongObj
• Tcl_GetLongFromObj
• Tcl_NewWideIntObj
• Tcl_DbNewWideIntObj
• Tcl_SetWideIntObj
• Tcl_GetWideIntFromObj
• Tcl_NewBignumObj
• Tcl_DbNewBIgnumObj
• Tcl_GetBignumFromObj
• Tcl_TakeBignumFromObj
• Tcl_SetBignumObj

Private Routines

• TclSetBooleanFromAny
• TclGetNumberFromObj
• TclSetBignumIntRep

Directly Depends On Public Routines From

• Tcl_Obj System
• string Object Type
• Parsing and Evaluation
• Panic

Directly Depends On Private Routines From

• Numbers

Discussion

Depends on Tcl_PrintDouble and TclFormatInt which ought to just be here, or in Numbers.

The TclGetNumberFromObj or some other scheme for similar function would be useful public.

Probably worth raising the question as to what degree the notion of a "wide integer" is a historical detour, and if there are other ways to get at integral types of different sizes that might be easier to use looking ahead.

Generating the string rep of a bignum scales very very very very badly. For large enough values we can expect decimal string rep generation to take years.