1. Including Graphics
- Posted by "Graeme." <hmi at POWERUP.COM.AU> Apr 23, 1998
- 587 views
Hi All, Just realized something. Due to Euphoria's ability to handle runtime calculated constants, if you have directly included data in ascii and/or compressed format you can declare the *TARGET* data as a constant and bypass the extra memory overhead. i.e. (using incbm.e) constant bitmap=ebm("^%V#*G#UG#*&G#*(&G#G......") Euphoria will recompress the data on execution then declare the RESULT as a constant. The source data will not be kept in memory (I assume). I'll update incbm.e to make use of this method as soon as I get time. One of those obvious ones that laughs at you when you eventually find it under the cushions on the sofa. Graeme.
2. Re: Including Graphics
- Posted by Robert Craig <rds at EMAIL.MSN.COM> Apr 23, 1998
- 564 views
Graeme writes: > Just realized something. > Due to Euphoria's ability to handle runtime calculated > constants, if you have directly included data in ascii > and/or compressed format you can declare the *TARGET* data > as a constant and bypass the extra memory overhead. > i.e. (using incbm.e) > constant bitmap=ebm("^%V#*G#UG#*&G#*(&G#G......") > Euphoria will recompress the data on execution then > declare the RESULT as a constant. The source data will > not be kept in memory (I assume). Your assumption is correct. After the constant assignment to bitmap, Euphoria will keep only the result of ebm(), and will free any other data that is no longer needed, including the string "^%V..." and any private variables within ebm(). Regards, Rob Craig Rapid Deployment Software