> On 19 Mar 2002 10:41:16 -0500, Ron Parker <ron### [at] povrayorg> wrote:
>> What, assembly-language-like bytecode isn't good enough for you?  Kids these
>> days...
> 
> My asked for my daughter. She likes building functions in macros and render in
> one pass ;-)
> 
>> I think at the moment that it's a bonus pack for patch writers.  I don't know
>> what the Team's plans are WRT the debugging features
> 
> http://news.povray.org/3c2caae6@news.povray.org

Well, there ya go then.  Straight from the horse's mouth.  Of course, since
it's just turned off with a compile-time switch, enterprising patch writers
will be able to turn it back on easily.

-- 
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbf 1}hollow interior{media{emission 3-T}}}#end 
Z(-x-x.2x)camera{location z*-10rotate x*90normal{bumps.02scale.05}}

Post a reply to this message

On 19 Mar 2002 11:11:22 -0500, Ron Parker <ron### [at] povrayorg> wrote:
> That documentation looks something like this:

and it's very similiar to 6.1.6.6 chapter :-)

ABX

Post a reply to this message

> On 19 Mar 2002 11:11:22 -0500, Ron Parker <ron### [at] povrayorg> wrote:
>> That documentation looks something like this:
> 
> and it's very similiar to 6.1.6.6 chapter :-)

I'm obviously missing something... there is no 6.1.6.6???

-- 
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}

Post a reply to this message

On 19 Mar 2002 11:26:13 -0500, Ron Parker <ron### [at] povrayorg> wrote:
> > > That documentation looks something like this:
> > 
> > and it's very similiar to 6.1.6.6 chapter :-)
>
> I'm obviously missing something... there is no 6.1.6.6???

It was supposed to be a joke since there is also no "else if(Token.Token_Id ==
STRING_LITERAL_TOKEN)" in my installation of documentation ;-)

ABX

Post a reply to this message

> On 19 Mar 2002 11:26:13 -0500, Ron Parker <ron### [at] povrayorg> wrote:
>> > > That documentation looks something like this:
>> > 
>> > and it's very similiar to 6.1.6.6 chapter :-)
>>
>> I'm obviously missing something... there is no 6.1.6.6???
> 
> It was supposed to be a joke since there is also no "else if(Token.Token_Id ==
> STRING_LITERAL_TOKEN)" in my installation of documentation ;-)

That's because you don't have the source code package, and all the 
documentation it customarily comes with.

-- 
plane{-z,-3normal{crackle scale.2#local a=5;#while(a)warp{repeat x flip x}rotate
z*60#local a=a-1;#end translate-9*x}pigment{rgb 1}}light_source{-9red 1rotate 60
*z}light_source{-9rgb y rotate-z*60}light_source{9-z*18rgb z}text{ttf"arial.ttf"
"RP".01,0translate-<.6,.4,.02>pigment{bozo}}light_source{-z*3rgb-.2}//Ron Parker

Post a reply to this message

Ron Parker wrote:
> 
> There is no source code package yet, right?  And when there is, there will
> be the same documentation I used to find this feature.
> 
> That documentation looks something like this:
> 
>     else if(Token.Token_Id == STRING_LITERAL_TOKEN)
> [...]

This of course was not what i meant, i meant a description of how to write
those assembly instructions.  A list of available commands and some
documented samples would help a lot.

Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 18 Mar. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message

On Tue, 19 Mar 2002 17:39:39 +0100, Christoph Hormann wrote:
> 
> 
> Ron Parker wrote:
>> 
>> There is no source code package yet, right?  And when there is, there will
>> be the same documentation I used to find this feature.
>> 
>> That documentation looks something like this:
>> 
>>     else if(Token.Token_Id == STRING_LITERAL_TOKEN)
>> [...]
> 
> This of course was not what i meant, i meant a description of how to write
> those assembly instructions.  A list of available commands and some
> documented samples would help a lot.

Oh.  Well, you're in luck there.  There is a significant amount of 
documentation for the bytecode in the appropriate source file.

-- 
#local R=<7084844682857967,0787982,826975826580>;#macro L(P)concat(#while(P)chr(
mod(P,100)),#local P=P/100;#end"")#end background{rgb 1}text{ttf L(R.x)L(R.y)0,0
translate<-.8,0,-1>}text{ttf L(R.x)L(R.z)0,0translate<-1.6,-.75,-1>}sphere{z/9e3
4/26/2001finish{reflection 1}}//ron.parker@povray.org My opinions, nobody else's

Post a reply to this message

Ron Parker wrote:
> 
> Oh.  Well, you're in luck there.  There is a significant amount of
> documentation for the bytecode in the appropriate source file.
> 

Great.

I'm eagerly waiting to see it...


Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 18 Mar. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message

Ron Parker <ron### [at] povrayorg> wrote:
> What, assembly-language-like bytecode isn't good enough for you?

  That's luxury!
  The only valid input for functions should be opcodes written in hexadecimal!

-- 
#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:
> > What, assembly-language-like bytecode isn't good enough for you?
>   That's luxury!
>   The only valid input for functions should be opcodes written in hexadecimal!

I'm wondering, what kind of instruction word this ASM-interpreter uses ...

are they more CISC- or more RISC- like ? ...

BTW: What 'bout self-modifying code ? ... that would be nice ... back to oldschool

Post a reply to this message