Skiba <abx### [at] babilonorg>  wrote:

>> You are confusing a declaration and
>> assignment statement here!
>
> From doc (6.2.6.2): "The #ifdef and #ifndef directives can be used to
> determine whether a specific element of an array has been declared."

And???  I see nothing about #undef here, so why would this be relevant?

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Skiba <abx### [at] babilonorg>  wrote:

>> It is an undefined symbol:
>> There is no symbol with the name "A[0][0]", only one with the name "A"!
>
> There is also no symbol with name "B" but when I replace #undef A[0][0] with
> #undef B then behaviour is different.

Yes, because "B" is a valid symbol name.  "A[0][0]" is not.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

On Tue, 22 Jan 2002 16:09:41 +0100, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> > There is also no symbol with name "B" but when I replace #undef A[0][0] with
> > #undef B then behaviour is different.
>
> Yes, because "B" is a valid symbol name.  "A[0][0]" is not.

The difference is too subtle for my English so I stay with "it is feature
request". Sorry for bothering - I just buy 1 GB of memory and use it as is :-(

ABX
--
disc{z,-z 5#macro O()asc(substr("-+((1*(,1,/.-,*/(,&.323/'1"e,1))*.1-4#declare
e=e-1;#end#local e=26;pigment{#local g=function(_){ceil(_)-_}function#local//X
k=function{pattern{object{sphere_sweep{linear_spline 13#while(e>0)<O(),O()//AB
>.01#end}}}}{k(g(atan2(x,y)),g(ln((y+x)^2+1e-5)),0)}}finish{ambient 1}}//POV35

Post a reply to this message

"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3c4d8084@news.povray.org...
> In article <9kpq4uk15iqbmu674hbamr6esvt5vhogbs@4ax.com> , W"odzimierz ABX
> Skiba <abx### [at] babilonorg>  wrote:
>
> >> You are confusing a declaration and
> >> assignment statement here!
> >
> > From doc (6.2.6.2): "The #ifdef and #ifndef directives can be used to
> > determine whether a specific element of an array has been declared."
>
> And???  I see nothing about #undef here, so why would this be relevant?
>

Well, it's relevant because it says "has been declared", not "has been
assigned".

I think this problem is a shortcoming in the docs rather than a bug. Whilst
no-one expects the docs to specify everything you can't do in pov, there are a
few cases when such "do nots" would be appropriate, and this would be one of
them. In this case, arrays should always talk about assignment of array
elements, not declarations, and a short sentance that array elements cannot be
#undefed could be added.

Are you always so rude? IMHO if experienced users can be confused by such
issues, God help the newbies.

Post a reply to this message

On Tue, 22 Jan 2002 16:08:45 +0100, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> > > You are confusing a declaration and
> > > assignment statement here!
> >
> > From doc (6.2.6.2): "The #ifdef and #ifndef directives can be used to
> > determine whether a specific element of an array has been declared."
>
> And???  I see nothing about #undef here, so why would this be relevant?

According to your answer perhaps should be "The #ifdef and #ifndef directives
can be used to determine whether a specific element of an array has been
_assigned_." But as I said in another post differences are too subtle for my
English and I finish wasting of your time. Sorry.

ABX

Post a reply to this message

Skiba <abx### [at] babilonorg>  wrote:

>> And???  I see nothing about #undef here, so why would this be relevant?
>
> According to your answer perhaps should be "The #ifdef and #ifndef directives
> can be used to determine whether a specific element of an array has been
> _assigned_." But as I said in another post differences are too subtle for my
> English and I finish wasting of your time. Sorry.

Hmm, it should indeed say assigned, that would make things much clearer.

Anyway, I think it isn't too much to add this feature as the actual error
message is generated in the function that does the removal of symbols and
nearly all releveant information is available there to add the feature (I
hope).  However, arrays aren't as "native" to the parser as they they appear
to the user...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Tom Melly <tom### [at] tomandlucouk> wrote:
: Are you always so rude? IMHO if experienced users can be confused by such
: issues, God help the newbies.

  Try to develope five different pov-related things at the same time as well
as trying to live your real life... It's not a surprise that this kind of
pressure can make you a bit testy.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

"Warp" <war### [at] tagpovrayorg> wrote in message news:3c4d8be8@news.povray.org...

>   Try to develope five different pov-related things at the same time as well
> as trying to live your real life... It's not a surprise that this kind of
> pressure can make you a bit testy.

I fully appreciate this - however, it does no-one any favours to let it go
uncommented.

Post a reply to this message

On Tue, 22 Jan 2002 15:20:44 -0000, "Tom Melly" <tom### [at] tomandlucouk> wrote:
> I think this problem is a shortcoming in the docs rather than a bug. Whilst
> no-one expects the docs to specify everything you can't do in pov, there are a
> few cases when such "do nots" would be appropriate, and this would be one of
> them. In this case, arrays should always talk about assignment of array
> elements, not declarations, and a short sentance that array elements cannot be
> #undefed could be added.

Especially that there is simple relation ifdef-undef in characters for non
native English users.

ABX

Post a reply to this message

In article <3c4d834c$1@news.povray.org> , "Tom Melly" <tom### [at] tomandlucouk>
wrote:

> Are you always so rude?

No, just a bit annoyed that so many "bugs" that get reported are feature
requests from back in the 3.1 days or/and other real bugs suddenly get
reported for 3.5 while nobody bothered to report them for 3.1 or 3.0 or even
earlier also they always existed (and you can't tell me no-one using POV-Ray
all the time noticed).  And of course, everybody expects to get their pet
bug fixed in the next beta...

Then there are those nice complaints why this and that feature hasn't been
integrated and people completely seem to forget that 3.5 is (unfortunately)
much, much, much more than just taking some patch and adding it to the
official source code.  It includes to find and fix all those bugs and
restrictions of those patches and to find solutions.  All this is then of
course expected to be done in no time and soon there are threads (even
outside news.povray.org) by people who complain that the beta period takes
"so long" also only half the time the 3.1 beta took passed so far.

In the middle of that one then has to start explaining why a particular
behavior is no bug but by design.  And the endless arguing is what really
takes so much time because one constantly has to check the source code to
make sure what is said is really correct.  Not that it takes much to start
the argument, just find some example that doesn't work as you expect and
call it a bug - someone will the be forced to look into it :-(

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message