Am Donnerstag, 21. April 2005 15:06 schrieb Anton Ertl: > Ralf Hautkappe wrote: ahh.... now i understand... it seems to be a beginners pitfall... but it is logic... do consumes stackitems if theres no dup for the inner loop me gets into trouble...
... off topic.... btw i find it hard to work with forth.. not because of forth is bad.... (no its too simple) because of myself used to work with complexer languages... you cant see the trees in the forrest.... my first kachel program was in pure latex. it works fine, but it was a bit unhandy providing parameters..... my second was in perl.... it produces latex output and parameter handling was flexible.... then i read about forth... and was surprised... so i coded a 3rd version it was shorter and more elegant than the perl programm but coding took 3 times longer... ( du to learning forth ) then i start reading thinking forth 4 days ago.... and now... i am coding the 4th version (because now the 3rd is ugly, unelegant, influenced by perl etc... ) it is a bit like zen.... thx for your help ralf > > i dont understand why there must be a stack underflow ( because ?do takes > > two items thats provided through the parameters 2 2 ) > > In the first Iteration of the outer loop the inner ?DO takes a 2. In > the next iteration it takes another stack item, but you did not > provide one => stack underflow. > > But that's a general Forth question, so I would recommend > news:comp.lang.forth. > > - anton > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
