19:04:04drmeisterOk, 11 places there - I can handle those.
19:04:12Bikeright now im' trying to do the printing but i don't really understand what bignum_to_string is doing
19:04:22Bikeit digs into the internals of a Str8Ns_sp
19:04:29Bikeand printing with tmpn is more involved than with mpz
19:04:56Bikei also don't understand why bignum_to_string is written like it can be called from lisp, but takes a StrNs_sp and an mpz_class as arguments
19:04:59drmeisterFeel free to ask questions. I remember that function.
19:05:23drmeisterThere is probably a translator for mpz_class.
19:06:16Bikeso printing in mpn is like this: first off you have to put in the minus sign yourself. secondly the string mpn actually gives you is made so that you have to translate it into the actual 0, 1, 2, etc characters
19:06:27Bikei can't just output it right into the buffer8 like this apparently does
19:06:41Bikeor well, i guess i could, but then i'd have to mutate it
19:09:04drmeisterWhich mpn function are you using?
19:10:08Bikempn_get_str. the documentation doesn't describe the output very well.
19:10:37Bikebasically if you have 123 as a bignum, the string will have (char)1, (char)2, and (char)3, rather than the actual 1 2 3 characters
19:11:29drmeisterUhuh - I would mutate it in place.
19:11:55drmeisterDump it into the string the way bignum_to_string does and then sweep through and add the '0' or 'A'
22:47:57Bikedon't totally understand why the fix worked but it did
23:47:02Bikedrmeister: also, it's not like using mpz is in itself a problem, it's just the assuming that the lisp arithmetic functions work directly with them. cando could effectively depend on GMP separately from clasp
2:06:45drmeisterNah - I'd like to use clasp's bignums. Cando isn't doing anything fancy with them.
2:07:17drmeisterSometimes you need bignums and if you don't have them - it's a PITA.
2:20:24Bikeit looked they were being managed like C++ objects, not lisp objects