"Recovering" Proxomitron's Source Code...
|
May. 12, 2018, 07:32 PM
Post: #31
|
|||
|
|||
RE: "Recovering" Proxomitron's Source Code...
The time since the last post was spent fixing as many of the bugs I introduced as I could find... and this post was made through the resulting Proxomitron
Since the code is pretty much the same, I don't think it makes all that much sense to change its name that much. Maybe Proxomitron 4.5R+ (for reverse-engineered/recompiled/reborn/re-xxx, and the '+' because it incorporates my SSL patches, and a few other things)? I believe it was originally based on 4.5J. I'll continue using it for a week or two and if no more bugs come up, release it here in a new thread so y'all can test! |
|||
The following 9 users say Thank You to amy for this post: chatterer, mizzmona, soccerfan, usr, Callahan, ProxRocks, Kye-U, zoltan, Styx |
May. 12, 2018, 08:26 PM
Post: #32
|
|||
|
|||
RE: "Recovering" Proxomitron's Source Code...
|
|||
The following 1 user says Thank You to JJoe for this post: mizzmona |
May. 13, 2018, 12:08 AM
Post: #33
|
|||
|
|||
RE: "Recovering" Proxomitron's Source Code...
BRAVO! Outstanding!!!
|
|||
May. 14, 2018, 08:33 AM
Post: #34
|
|||
|
|||
RE: "Recovering" Proxomitron's Source Code...
Yes ... not changing the name too much seems to make more sense. The 'R' can keep it short and close to Scott Lemon's original idea and work.
I'm just a 'foot soldier' marching along ... Headquarters says 'march', so we march. I'll probably be marching through your area someday. ... |
|||
Aug. 25, 2019, 09:07 AM
Post: #35
|
|||
|
|||
RE: "Recovering" Proxomitron's Source Code... | |||
« Next Oldest | Next Newest »
|