Thank you! I've tried it and it perfectly suits my present needs!
Now I can make it transparent for somebody who does not want to know anything about underlying mechanisms to run my code. -- Sergey On Sat, 24 Sep 2005 21:40:52 +0200 Bernd Paysan <[EMAIL PROTECTED]> wrote: > On Friday 02 September 2005 23:37, Sergey Plis wrote: > > on the command line I have to do > > > > ~# xbigforth -m 1G test.m > > > > Is there a way to allocate OS memory when xbigforth has already > > started? If not then may be you know how in bash pass parameters to > > the interpreter written in the first line of the script? > > I've changed the command interpreter of bigforth so that it can > accept settings with a '=' in between option and argument, and a ',' > to separate several options. That should allow to put several options > into the single allowed option of a script file, e.g. > > #! xbigforth -m=900M,-d=8M > > Tell me if that's useful enough (there are still some limitations > concerning the -v option, and the image option has to come last). > > -- > Bernd Paysan > "If you want it done right, you have to do it yourself" > http://www.jwdt.com/~paysan/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
