OpenEuphoria

Re: direction

• Posted by bfurniss <bfurniss at IHUG.CO.NZ> Mar 18, 2000
• 502 views

At 01:50 PM 3/17/00 -0600, you wrote:
>----- Original Message -----
>From: "bfurniss" <bfurniss at IHUG.CO.NZ>
>To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
>Sent: Friday, March 17, 2000 6:32 AM
>Subject: direction
>
>
>>
>>   I've attached a file that outlines one direction that software
>>  development around Euphoria might go.
>
>I can't understand why this was sent as an attachment, but whatever...
>

  Don't worry , just a general message to ALL , until I can tell who's
 interested in what I'm attempting with Euphoria.
  A little software , occassionally ,might be more appropriate.

>I need to bite my tongue a bit and comment on the 32bits per ascii byte of
>storage. While i do like the idea for the options it gives, if it's possible
>to specify a smaller set of options to reduce the memory requirements for
>keeping data in memory, i'd like that too. Right now, if i wish to keep a
>50Meg file in a sequence in memory all the time, Eu wants 200Meg for it,
>then i add in 64Meg of windoze, and another 32meg for applications to play
>in, and i must have 296Meg of ram on the puter. <gasp> I have the 96Meg, but
>adding a 256Meg module is simply out of the question for the foreseeable
>future. Seems my only option is grabbing memory, and peeking and poking the
>8bits of ascii?
>
>Kat

    I hadn't realized that Euphoria stored ASCII like that , and yet you
  don't have a selection of good fonts in most any graphics_mode( ).
    Peek and Poke don't use machine.e routines therefore they're going to
  be pretty portable.
    Make a procedure to do this and tuck the thing away in an include file
  somewhere until you get an answer from somewhere.
    Of course TYPE checking might determine how many bits are being used
  in any particular instance.