| 13 Mar 2006 09:29:48 am by KermMartian |
|
Quote |
| Yup, you can store up to 14 digits in any real or complex part; it displays only 12, but you can access up to 14 from a prog. |
| 13 Mar 2006 09:48:41 am by elfprince13 |
|
Quote |
| which would make it faster to just use 2 reals. |
| 13 Mar 2006 10:04:36 am by KermMartian |
|
Quote |
| Eh, generally. However, you can save a couple of bytes by using complex instead of real numbers for 1 list instead of 2. |
| 13 Mar 2006 01:07:02 pm by elfprince13 |
|
Quote |
that is handy  |
| 13 Mar 2006 01:08:57 pm by KermMartian |
|
Quote |
| If you take a look at the latest released beta of Brix Builder, you'll see I did the polygon coordinates for it with that schema. |
| 13 Mar 2006 01:12:19 pm by elfprince13 |
|
Quote |
| cool. I personally like the extraction from a real trick better though. |
| 13 Mar 2006 01:15:09 pm by KermMartian |
|
Quote |
| Yeah, that's not bad. One of the problems with the complex "compression" though is that it takes far too many clock cycles to extract the real(/cplx( parts. |
| 13 Mar 2006 05:10:02 pm by Kuro |
|
Quote |
| They are still easier to manipulate than 12-digit real numbers. |
| 13 Mar 2006 05:15:00 pm by Radical Pi |
|
Quote |
| I prefer the combinations of 10^() and fPart(). |
| 13 Mar 2006 05:23:23 pm by Kuro |
|
Quote |
| ...Which together use the same number of clock cycles as ipart()/fpart(). |
| 19 Mar 2006 02:00:19 pm by KermMartian |
|
Quote |
| 10^( uses slightly less, actually. |
| 20 Mar 2006 04:02:56 pm by Kuro |
|
Quote |
 I didn't know that. I may have to revise my tetris program now. |
