[Omake] 2 questions about .SCANNER rules and a possible bug report

[Nick]

Thank you Aleksey.
>From your explanation about .SUBDIRS and dep. generation it's clear to
me that there have
been no design oversights in omake (in any critical areas that I care
about).
As for the infinite rule generation and exhaustion of all available
memory when "while"
indentation is the same as i=$(add $,1) maybe you should raise a warning
beyound a certain
threshhold (number of rules, or amount of virtual memory) because as
soon as physical
memory is exhausted and the machine starts swapping it may be difficult
to regain control
of the xterm and kill omake.
But this is low priority as far as I am concerned.
Again omake is nothing short of amazing and makes me wonder why there
are lemmings out there
who still use "recursive" old fasioned build methods. O well, this is
life.
Now that I've collected enough info to keep going you won't hear from me
for a while.
Bye and thanks for the help.


> > One final note: if the indentation of "i = $(add $i, 1) " matches the
> > indentation of "while" the program goes into unbounded recursion and
> > gobbles up all available memory (>2GB on my machine).
> > Obviously such indentation is wrong but nevertheless I consider the
> > omake behaviour in that case a bug.
> 
> I would disagree - you wrote a "valid" piece of code instructing OMake 
> to run in an infinite loop, constantly adding new rules. Of course, 
> OMake runs out of memory...
> 
> Aleksey
> _______________________________________________
> Omake mailing list
> Omake at metaprl.org
> https://lists.metaprl.org/mailman/listinfo/omake
-- 
  Nick
  z508617 at ftml.net

-- 
http://www.fastmail.fm - I mean, what is it about a decent email service?