php 4 version 3 coming?
Moderators: Chris Corbyn, General Moderators
php 4 version 3 coming?
Everybody uses php 4 and the market is thungry for this. Heck, they'd pay hand over first. I'm just wondering when a php 4 version that allows variables in the header and personalization will be available.
Thank you
Thank you
- Kieran Huggins
- DevNet Master
- Posts: 3635
- Joined: Wed Dec 06, 2006 4:14 pm
- Location: Toronto, Canada
- Contact:
- Chris Corbyn
- Breakbeat Nuttzer
- Posts: 13098
- Joined: Wed Mar 24, 2004 7:57 am
- Location: Melbourne, Australia
LOL. It's a headache - I got a bit over-complex on my use of references in the document reformatting code - I'll say that much. I'm also tackling the issue of what I do where I threw references in PHP5, because trigger_error() won't have the same effect.
I think I'm at a point in the current conversion to go "svn delete branches/php4/v3" and start over with a clear head.
I'm sorry I can't give an accurate date for a release; I've learnt not to commit myself to strict deadlines for volunteer projects as they often get in the way of other jobs. I was going to work on a Java project today which I'm releasing shortly but I'll do Swift instead
First - I need a cup of tea! I just got out of bed at 12:00 on a Sunday... but I have Monday off work! w00t!
I think I'm at a point in the current conversion to go "svn delete branches/php4/v3" and start over with a clear head.
I'm sorry I can't give an accurate date for a release; I've learnt not to commit myself to strict deadlines for volunteer projects as they often get in the way of other jobs. I was going to work on a Java project today which I'm releasing shortly but I'll do Swift instead
- Chris Corbyn
- Breakbeat Nuttzer
- Posts: 13098
- Joined: Wed Mar 24, 2004 7:57 am
- Location: Melbourne, Australia
Actually, the earlier version seemed to work great, the only real issue (I can personalize, just by doing a loop through every record
and I use the anti-flood plugin) was not being able to customize the from info easily.
IS there a way to fix that? If this was included in my software I'd do cartwheels ,but I had to disable it becasue many people wouldn't know what to do (pathetic, but true)
Just curious. I agree you shouldn't force yourself to do anything with volunteer work. But I know a lot of people who would gladly donate if this feature were avail, myself included. It's an AMAZING piece of software. Worst case I'll disable it if I sense they didn't make the appropriate changes.
and I use the anti-flood plugin) was not being able to customize the from info easily.
IS there a way to fix that? If this was included in my software I'd do cartwheels ,but I had to disable it becasue many people wouldn't know what to do (pathetic, but true)
Just curious. I agree you shouldn't force yourself to do anything with volunteer work. But I know a lot of people who would gladly donate if this feature were avail, myself included. It's an AMAZING piece of software. Worst case I'll disable it if I sense they didn't make the appropriate changes.
- Chris Corbyn
- Breakbeat Nuttzer
- Posts: 13098
- Joined: Wed Mar 24, 2004 7:57 am
- Location: Melbourne, Australia
- Chris Corbyn
- Breakbeat Nuttzer
- Posts: 13098
- Joined: Wed Mar 24, 2004 7:57 am
- Location: Melbourne, Australia
UPDATE: I have successfully converted the entire library to PHP4. I haven't done EasySwift yet, because before I do that I want to go over the entire conversion and implement a work-around for the use of exception in PHP5. At the moment I have (deliberately, just to make my unit tests pass) used trigger_error() interspersed with the @ error surpression operator which is not very clean or fast. I'll likely put the code into the trunk by the end of today. As a matter of caution and for the sake of simplicity I suggest people *always* use the & reference operator when creating new instances of the classes in the library when running under PHP4. For the mostpart you wouldn't notice anything odd if you didn't, but if you're taking advantage of bit of the new API you will do.
EDIT | The changes I'm adding for error handling aren't massive, I'm just going to centralise the behaviour where I'm using trigger_error() so I can "catch" the error without having to use set_error_handler().
EDIT | The changes I'm adding for error handling aren't massive, I'm just going to centralise the behaviour where I'm using trigger_error() so I can "catch" the error without having to use set_error_handler().