|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Progress on povclipse2 has moved along.
I have basically implemented SDL as one giant 1000 line tokenizing
function. I keep looking at how to refactor that, but, it's one
function that just recursively builds a parsed tree.
The tooltips are cool. Wolfgang did all the heavy eclipse lifting on
those, but then only looked at surrounding words in the document for
triggers. I can trigger on any word in the project, and show the
results of any simple math.
You can click on any word and go to it's definition, on any file in the
project.
It displays errors if you supply the wrong number of parameters to a
macro, among other errors.
I had to break spec only once...
This is evil, yet legal in SDL:
#declare a = array[5]
These two are fine...
#declare a = array[5];
#declare a = array[5] {blah}
I still have to rebuild the outline view and completion processor.
I wrote this just to better work with the 122 main files of my animation
(not including the java generated per-frame files). I've just got
povclipse2 to the point where I can actually use it for myself. It is
cool to be able to ctrl-click through the include tree
TPTB can yell at me for attaching 20KB worth of pics in a non-binaries
newsgroup. The rest of you can laugh at my M$Paint worthy cursor pasted
on the tooltips.
dik
Post a reply to this message
Attachments:
Download 'povclipse2tooltipvector.png' (12 KB)
Download 'povclipse2tooltipcolor.png' (10 KB)
Preview of image 'povclipse2tooltipvector.png'
Preview of image 'povclipse2tooltipcolor.png'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 17.01.2017 um 10:53 schrieb dick balaska:
> Progress on povclipse2 has moved along.
> I have basically implemented SDL as one giant 1000 line tokenizing
> function. I keep looking at how to refactor that, but, it's one
> function that just recursively builds a parsed tree.
...
> I had to break spec only once...
Wow, that's impressive!
> TPTB can yell at me for attaching 20KB worth of pics in a non-binaries
> newsgroup. The rest of you can laugh at my M$Paint worthy cursor pasted
> on the tooltips.
TBTB have better things to do than to worry about 20KB (could just as
well be a long text post, right?) -- for instance laughing at your
M$Paint worthy cursor ;)
Or, for that matter, wondering whether your colour tooltip does proper
gamma correction. /That/ is something one of TPTB is genuinely (semi-)
worried about. (Does it honor `assumed_gamma`? Does it properly handle
`srgb`? Is it tasty? Is it scruuuuuumptious?)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 2017-01-17 07:08, also sprach clipka:
> wondering whether your colour tooltip does proper
> gamma correction.
Gamma is an illusion.
(I was actually wondering if it does filter and transmit correctly,
looks funky to me)
--
dik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 2017-01-17 07:08, also sprach clipka:
> Am 17.01.2017 um 10:53 schrieb dick balaska:
>> I had to break spec only once...
>
> Wow, that's impressive!
>
Eh crap. Two other failures (that I've used in my own code).
Basically, I can't deal with mixed (broken) nesting between directives
and objects.
1)
#declare MyObject=
#if (1)
box {0,1}
#else
box {2,3}
#end
2)
#declare MyObject=
#if (needUnion)
union {
#end
#for (I,0,needUnion)
box {0,1}
#end
#if (needUnion)
}
#end
--
dik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/17/2017 04:53 AM, dick balaska wrote:
> Progress on povclipse2 has moved along.
> I have basically implemented SDL as one giant 1000 line tokenizing
> function. I keep looking at how to refactor that, but, it's one
> function that just recursively builds a parsed tree.
>
I see a "parseTest.pov" in one of your attached images. I'm interested
in a relatively complete, reasonably concise, set of SDL test files I
might run when twiddling with the parser.
Is there a collection of such test files for the povclipse<n> work ?
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 2017-02-16 11:14, also sprach William F Pokorny:
> On 01/17/2017 04:53 AM, dick balaska wrote:
>
> I see a "parseTest.pov" in one of your attached images. I'm interested
> in a relatively complete, reasonably concise, set of SDL test files I
> might run when twiddling with the parser.
>
> Is there a collection of such test files for the povclipse<n> work ?
>
Sorry, no. The closest I have is a single file that I process through
JUnit, so not much use to you. It contains things like this:
@@testDecls@@
// test various decls
#declare a = 0; // 0
#declare b = 1; // 1
#declare c = a + b; // 1
#declare d = c + (a+b); // 2
#declare e = f; // error
@@
@@testDeclsAfter@@
// Test that a token defined after use is not seen.
#declare a = 0;
#declare b = c; // error
#declare c = 1;
@@
--
dik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |