From: Sam Steingold <sds@gn...>  20071031 18:33:51

BEGIN PGP SIGNED MESSAGE Hash: SHA1 Lonnie Cumberland wrote: > Don't really know how to modify the algorithm and presume that would > require a recompiling of the Clisp sources which seems like a lot of > additional work and large source code programming learning curve. I was talking about _your_ algorithm. you can try to modify it to use smaller arrays. Sam. A: Because it messes up the order in which people normally read text. Q: Why is topposting such a bad thing? A: Topposting. Q: What is the most annoying thing in email? BEGIN PGP SIGNATURE Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla  http://enigmail.mozdev.org iD8DBQFHKMqFPp1Qsf2qnMcRAkC4AKCAg+ZqSlY9nCfoFmhRoOu+9sSLbgCfQAiL +IGNbCfQFp0N5RgIjA1DofQ= =RtBL END PGP SIGNATURE 
From: Lonnie Cumberland <lonnie@ou...>  20071031 17:35:16

Greetings All, I have just started experimenting with clisp on my WindowsXP machine with a small number theory problem is HMPQS factoring. The lisp code runs great for reasonably small numbers (ie... 40  60 digits) but when I try to put in a test number that is on the order of 150  200 digits I get an error: ***  MAKEARRAY: dimension 70341185 is not of type '(INTEGER 0 (,ARRAYDIMENSIONLIMIT)) How can I check the current array dimenstion limit? How can I change the limit to handle the larger arrays needed for my research? Sincerely and have a great day, Lonnie T. Cumberland Email: Lonnie@... Lonnie_Cumberland@... Lonnie.Cumberland@... "Helping to improve our communities, one by one......" 
From: Sam Steingold <sds@gn...>  20071031 18:00:49

BEGIN PGP SIGNED MESSAGE Hash: SHA1 Lonnie Cumberland wrote: > Greetings All, > > I have just started experimenting with clisp on my WindowsXP machine > with a small number theory problem is HMPQS factoring. > > The lisp code runs great for reasonably small numbers (ie... 40  60 > digits) but when I try to put in a test number that is on the order of > 150  200 digits I get an error: > > ***  MAKEARRAY: dimension 70341185 is not of type '(INTEGER 0 > (,ARRAYDIMENSIONLIMIT)) > > How can I check the current array dimenstion limit? evaluate ARRAYDIMENSIONLIMIT > How can I change the limit to handle the larger arrays needed for my > research? ARRAYDIMENSIONLIMIT is determined by the CPU type. see http://clisp.cons.org/impnotes/arrayelts.html BEGIN PGP SIGNATURE Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla  http://enigmail.mozdev.org iD8DBQFHKMLDPp1Qsf2qnMcRAtb0AKCXPMwYSOk2eE7bKsEGBNgPGnYwJACdEOIV EGBPTSrq/r4yYwLpnL9JtyQ= =KJ6N END PGP SIGNATURE 
From: Lonnie Cumberland <lonnie@ou...>  20071031 18:07:17

Thanks for the information. I have to figure out how to "evaluate ARRAYDIMENSIONLIMIT", but from what I can now see, I will have to step up to a 64 bit machine in order to work with larger numbers. Thanks again and have a great day, Lonnie T. Cumberland Email: Lonnie@... Lonnie_Cumberland@... Lonnie.Cumberland@... "Helping to improve our communities, one by one......" On Wed, October 31, 2007 13:00, Sam Steingold wrote: > BEGIN PGP SIGNED MESSAGE > Hash: SHA1 > > > Lonnie Cumberland wrote: > >> Greetings All, >> >> >> I have just started experimenting with clisp on my WindowsXP >> machine with a small number theory problem is HMPQS factoring. >> >> The lisp code runs great for reasonably small numbers (ie... 40  >> 60 >> digits) but when I try to put in a test number that is on the order >> of 150  200 digits I get an error: >> >> >> ***  MAKEARRAY: dimension 70341185 is not of type '(INTEGER 0 >> (,ARRAYDIMENSIONLIMIT)) >> >> >> How can I check the current array dimenstion limit? >> > > evaluate ARRAYDIMENSIONLIMIT > >> How can I change the limit to handle the larger arrays needed for >> my research? > > ARRAYDIMENSIONLIMIT is determined by the CPU type. > see http://clisp.cons.org/impnotes/arrayelts.html > > BEGIN PGP SIGNATURE > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla  http://enigmail.mozdev.org > > > iD8DBQFHKMLDPp1Qsf2qnMcRAtb0AKCXPMwYSOk2eE7bKsEGBNgPGnYwJACdEOIV > EGBPTSrq/r4yYwLpnL9JtyQ= > =KJ6N > END PGP SIGNATURE > > 
From: Lonnie Cumberland <lonnie@ou...>  20071031 18:12:30

Oops..... sorry for the double post.... Sincerely and have a great day, Lonnie T. Cumberland Email: Lonnie@... Lonnie_Cumberland@... Lonnie.Cumberland@... "Helping to improve our communities, one by one......" On Wed, October 31, 2007 13:11, Lonnie Cumberland wrote: > Thanks for the information. > > > I have to figure out how to "evaluate ARRAYDIMENSIONLIMIT", but > from what I can now see, I will have to step up to a 64 bit machine in > order to work with larger numbers. > > Thanks again and have a great day, > Lonnie T. Cumberland > > > Email: Lonnie@... > Lonnie_Cumberland@... > Lonnie.Cumberland@... > > > "Helping to improve our communities, one by one......" > > > On Wed, October 31, 2007 13:00, Sam Steingold wrote: > >> BEGIN PGP SIGNED MESSAGE >> Hash: SHA1 >> >> >> >> Lonnie Cumberland wrote: >> >> >>> Greetings All, >>> >>> >>> >>> I have just started experimenting with clisp on my WindowsXP >>> machine with a small number theory problem is HMPQS factoring. >>> >>> The lisp code runs great for reasonably small numbers (ie... 40  >>> 60 >>> digits) but when I try to put in a test number that is on the >>> order of 150  200 digits I get an error: >>> >>> >>> ***  MAKEARRAY: dimension 70341185 is not of type '(INTEGER 0 >>> (,ARRAYDIMENSIONLIMIT)) >>> >>> >>> >>> How can I check the current array dimenstion limit? >>> >>> >> >> evaluate ARRAYDIMENSIONLIMIT >> >>> How can I change the limit to handle the larger arrays needed for >>> my research? >> >> ARRAYDIMENSIONLIMIT is determined by the CPU type. >> see http://clisp.cons.org/impnotes/arrayelts.html >> >> BEGIN PGP SIGNATURE >> Version: GnuPG v1.4.6 (GNU/Linux) >> Comment: Using GnuPG with Mozilla  http://enigmail.mozdev.org >> >> >> >> iD8DBQFHKMLDPp1Qsf2qnMcRAtb0AKCXPMwYSOk2eE7bKsEGBNgPGnYwJACdEOIV >> EGBPTSrq/r4yYwLpnL9JtyQ= >> =KJ6N >> END PGP SIGNATURE >> >> >> > > > >  >  > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. Download your FREE copy of Splunk now >> > http://get.splunk.com/ > _______________________________________________ > clisplist mailing list clisplist@... > https://lists.sourceforge.net/lists/listinfo/clisplist > > 
From: Sam Steingold <sds@gn...>  20071031 18:20:25

BEGIN PGP SIGNED MESSAGE Hash: SHA1 Lonnie Cumberland wrote: > Thanks for the information. welcome > I have to figure out how to "evaluate ARRAYDIMENSIONLIMIT", type ARRAYDIMENSIONLIMIT (any case) and hit Enter (or Return) and CLISP will print the value. > but from > what I can now see, I will have to step up to a 64 bit machine in > order to work with larger numbers. either that or modify the algorithm. Sam. BEGIN PGP SIGNATURE Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla  http://enigmail.mozdev.org iD8DBQFHKMdfPp1Qsf2qnMcRAuP3AJ9IBptwiTahLzFoIL5FJlZiCN3PWACgjpis /GxHl61MWhEUM6IDOaPll8c= =2pvS END PGP SIGNATURE 
From: Lonnie Cumberland <lonnie@ou...>  20071031 18:25:15

Don't really know how to modify the algorithm and presume that would require a recompiling of the Clisp sources which seems like a lot of additional work and large source code programming learning curve. Sincerely and have a great day, Lonnie T. Cumberland Email: Lonnie@... Lonnie_Cumberland@... Lonnie.Cumberland@... "Helping to improve our communities, one by one......" On Wed, October 31, 2007 13:20, Sam Steingold wrote: > BEGIN PGP SIGNED MESSAGE > Hash: SHA1 > > > Lonnie Cumberland wrote: > >> Thanks for the information. >> > > welcome > >> I have to figure out how to "evaluate ARRAYDIMENSIONLIMIT", >> > > type ARRAYDIMENSIONLIMIT (any case) and hit Enter (or Return) and > CLISP will print the value. > > >> but from what I can now see, I will have to step up to a 64 bit >> machine in order to work with larger numbers. > > either that or modify the algorithm. > > Sam. > > > BEGIN PGP SIGNATURE > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla  http://enigmail.mozdev.org > > > iD8DBQFHKMdfPp1Qsf2qnMcRAuP3AJ9IBptwiTahLzFoIL5FJlZiCN3PWACgjpis > /GxHl61MWhEUM6IDOaPll8c= > =2pvS > END PGP SIGNATURE > > 
From: Sam Steingold <sds@gn...>  20071031 18:33:51

BEGIN PGP SIGNED MESSAGE Hash: SHA1 Lonnie Cumberland wrote: > Don't really know how to modify the algorithm and presume that would > require a recompiling of the Clisp sources which seems like a lot of > additional work and large source code programming learning curve. I was talking about _your_ algorithm. you can try to modify it to use smaller arrays. Sam. A: Because it messes up the order in which people normally read text. Q: Why is topposting such a bad thing? A: Topposting. Q: What is the most annoying thing in email? BEGIN PGP SIGNATURE Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla  http://enigmail.mozdev.org iD8DBQFHKMqFPp1Qsf2qnMcRAkC4AKCAg+ZqSlY9nCfoFmhRoOu+9sSLbgCfQAiL +IGNbCfQFp0N5RgIjA1DofQ= =RtBL END PGP SIGNATURE 