1. That's what I've warned about from the beginning, that outside the complete project environment the error probably wouldn't occur. 2. I understand this completely, naturally. I would like to thank everybody spending time in reading my posts, particulary you, Jay. But that's why I would like to give you, or anyone else for that matter, an attended tour through the project. 3. I'm beeing pushed to present results, writting comments in my code would take almost twice the time writing the code itself. And in most cases, it's faster just to read my code instead of reading the comment. And finally, you wouldn't be able to read my comments, as my comments would be in dutch. Happy Thanksgiving back at you! On 11/23/05, Jay Blanchard <jay.blanchard@xxxxxxxxxxx> wrote: > > [snip] > Example is still quite large, all database functionality and other > arbitrary > code has been stripped. Over 50.000 lines of code have been reduced to a > few > hundred. Example can be downloaded here: > > http://213.10.83.232/example.tar > > Explanation of example: > > - When you load index.php, the involved objects will be loaded into your > session. > - If you use the "reset" link, the objects will be reinitialized. > - Continue just reloads index.php, objects will just wakeup from the > session > - You can change the title of the fs_ssl object, via the text input > - Underneath the submit button, the current title of fs_ssl is displayed > - The error that occurs in the real project: > On changing (submitting) the title of ssl, the sso->properties array gets > overwritten, this does not happen with this example > > Further, just explore the code to see what I'm doing exactly, if you need > more comment on what i'm doing, I will add comments to the example source > code. > [/snip] > > As soon as I have several hours of time to spare *cough* I will explore > the > code *cough*. > > 1. If the error does not occur with this example the situation you > originally described becomes non-reproducable. If we cannot reproduce the > error we have no chance of offering a solution. As you add things back > into > this example code, when does it break? > 2. The folks on this list are here to help, but I don't think that anyone > has time to sort through 100's of lines of code looking for what may be a > potential error, without wanting to charge a consulting fee. > 3. You have no comments in your example code? Brilliant! > > I know that I am being sarcastic here. > > I (and others) really would like to help, but I need you to help me (us) > do > that. I understand that the code is sensitive (company copyright/work > product issues) and lengthy. I strongly suspect that the application may > be > overly complex (based on a quick read through the code) and that you could > accomplish that which you are trying to do without being so obsfuscate. I > also think that you should send the information you have given us thus far > to the PHP-DEV list (http://www.php.net/mailinglists) and see what > response > that they have to offer given your assertion that the compiler is broken. > It > is more likely that someone lurking that list will be aware of problems > like > this where the compiler is concerned. > > Happy Thanksgiving! > > >
