MCStas

[Andrew Garrett]

Kristian,

  OK, this is coming along, well, sort of...  MCStas is now opening and reading
files properly, and the problem seems to be in mem...  I've turned on verbose
parser, and here are the last couple of lines that are coming out.

Reducing via rule 25 (line 286), "COMPONENT" TOK_ID '=' TOK_ID actuallist place
orientation  -> component
state stack now 0 2 5 7 11 15 22 34 45 54 58 61
Entering state 64
Reducing via rule 24 (line 279), complist component  -> complist
state stack now 0 2 5 7 11 15 22 34 45 54 58
Entering state 61
Reading a token: Next token is 262 ("COMPONENT")
Shifting token 262 ("COMPONENT"), Entering state 63
Reading a token: Next token is 278 (TOK_ID)
Shifting token 278 (TOK_ID), Entering state 66
Reading a token: Next token is 61 ('=')
Shifting token 61 ('='), Entering state 67
Reading a token: Next token is 278 (TOK_ID)
Shifting token 278 (TOK_ID), Entering state 68
Reading a token: Next token is 40 ('(')
Shifting token 40 ('('), Entering state 69
Reading a token: Next token is 41 (')')
Reducing via rule 32 (line 348),  -> actuals


Fatal error: memory exhausted during allocation of size 8000.

Program aborted.


  The machine I'm using has 32 MB RAM, and I'm wondering if this is enough.  I have
not yet traced the memory handling all that well, I'll admit - and with DOS's
insistence on stack vs. heap memory use, it is possible that I can fix this by
playing around with the mem functions.  Still, how much memory do you have on your
machines, and do you have any measurement of how much you need?

  Thanks,

  Drew Garrett