Re: Unifont static compiled and stack size...

["Jeffrey R.Carter" <spam.jrcarter.not@spam.acm.org.not>]

On 2023-08-14 17:10, Micah Waddoups wrote:
> 
> Jeff, you missed a digit - it's five F's  16#FFFFF# because that is as high as Unifont goes in my copy of the hex file.  Of course the technique should be able to go higher if that changes, but Unicode is pretty exhaustive as it is and Unifont is meant to keep up with every version and addition to the Unicode code points, so I sincerely hope for no trouble for a while yet.  I checked, and it seem my system has about 8 megabytes as the stack size limit, so with the ranges left empty it is not 32 megabytes, but still pretty big.  Good looking code, by the way.  Very easy to read.  Mine is appended, but it was really a quick hack of a job with too little sleep.  I probably should have done a Z Shell script (maybe take 20 seconds?), but I thought the two second efficiency of writing a compiled composer was worth it ...somehow...

You're right. Sorry for misreading that. But increasing Code_Point to include 
16#F_FFFF# still works for me.

Unicode defines code points up to 16#10_FFFF#, but perhaps those over 16#F_FFFF# 
are unused. Increasing Code_Point to include 16#10_FFFF# still works for me. 
That's 34 MB. It won't fit on the stack, but luckily library-level constants 
aren't allocated on the stack.

-- 
Jeff Carter
"I wave my private parts at your aunties."
Monty Python & the Holy Grail
13