Re: [Gnash-commit] gnash ChangeLog server/movie_root.cpp server/as...

[Benjamin Wolsey]

> >     
> >             Real-life cases sometimes show different behaviour from what's
> >             expected when the limit is very low. This may be for other
> >             reasons than the stack limit. Probably it's more important that 
> >             Gnash have a sensible policy with recursion than compatibility 
> > in
> >             every regard (though this would be good too), as it's an
> >             undocumented feature and tends to be used to extend the 
> > recursion
> >             limit when required, not for achieving fine-grained effects.
> 
> Speaking of which, should we (or do we already) set an upper-limit  for 
> limits ?
> I guess we should have at least a compile-time limit, plus a user-defined 
> one...
> 
> --strk;

The limit's upper-limit is limited to the limit 65535 by the type
(uint16_t), which seems fair enough (admittedly quite large, but still
limited) for a compile-time limit. User-defined limits from gnashrc are
on their way.

-bwy

signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil