2.58 bug?

[jmac698]

The first line doesn't work:
#blankclip(color_yuv=$118080,pixel_type="YUY2").subtitle(string(last.width))
blankclip(color_yuv=$118080,pixel_type="YUY2")
subtitle(string(last.width))
Shouldn't it work?

[Gavino]

No, last is not set until the end of the statement, so last is undefined in subtitle on the first line.

[jmac698]

Ok, call it a feature.. however I would *like* it to work that way. The documentation on "." should be updated, at least.

[StainlessS]

Jmac698,
This is a public endeavour, you can you update the wiki yourself with features.
I personally dont know how to. But you are very young, and will adapt,
Resistance it is futile, well at least not very productive.
You will adapt. (or die).

[jmac698]

I was thinking of the manual that comes with it. thats a little harder, I'd probably have to learn some repository system. not as easy as a wiki.

[Gavino]

Ok, call it a feature.. however I would *like* it to work that way. The documentation on "." should be updated, at least.
It can't work that way, since
blankclip(color_yuv=$118080,pixel_type="YUY2").subtitle(string(last.width))
is just another way of writing
subtitle(blankclip(color_yuv=$118080,pixel_type="YUY2"), string(last.width))
and you wouldn't expect 'last' to be taken from blankclip there, would you?

Also, if you wrote
x = blankclip(color_yuv=$118080,pixel_type="YUY2").subtitle(string(x.width))
you would expect the value of 'x' used in subtitle to be the previous value (if any) of x.
Implicit assignment to 'last' is no different. Your line is defined to mean
last = blankclip(color_yuv=$118080,pixel_type="YUY2").subtitle(string(last.width))

This is explained in the documentation, see
http://avisynth.org/mediawiki/Grammar
(also available on your hard disk in 'C:/Program Files/AviSynth 2.5/Docs/English/syntax_ref.htm')
and, in more detail,
http://avisynth.org/mediawiki/The_full_AviSynth_grammar#Expressions
http://avisynth.org/mediawiki/The_full_AviSynth_grammar#Statements

[Wilbert]

I was thinking of the manual that comes with it. thats a little harder, I'd probably have to learn some repository system. not as easy as a wiki.
If you think the documentation is not sufficient you can update the wiki. I always copy those changes to the offline documentation.

[jmac698]

Ahh, well that's a bit easier. I'll look for the spot that mislead me. I believe it was a page that suggested something about "." is equivalent to putting things on two lines.
Of course your explanation makes sense.
There are some things I'd like to add to the manual, I assume there's some kind of peer review? I certainly would want some kind of editorial insight.