Goodbye $phpEx

[igorw]

Any text editor nowdays allows recursive redectory searching and replacing. And i am pretty sure that meik (not miek) is not using dreamweaver for his coding. I would have also suggested that he used a commandline tool, as craig noted.

You could also still use the shorthand:

Code: Select all

append_sid('includes/functions.'); 

Just like including a language file, you can put folders in there.

You would however not link to the includes folder, and neither would you put a dot at the end. Geez, i rewrote my reply three times until i had understood what you're trying to say.

[Masterhand]

Well, this is sorta a nice change. There won't be any more $phpEx typos, and no confusing with variables, I once [somehow ] defined $phpEx as the amount of user points... But anyways, this is an intresting change. I wonder how the MOD developers feel.

[harmlessgoat22]

Theres going to be a lot of MOD updating

[Masterhand]

Theres going to be a lot of MOD updating

Yup, all of my scripts use it . I might even get a head start and start to revise them to 3.1 standards when the first stable public release comes out.

[harmlessgoat22]

I would, but then if I add anything to the MOD, i have to change it twice...so...I'll just wait until 3.2 is released.

[igorw]

I would probably wait until RC1 is out. a) Less adjustment work. b) Maybe somebody makes some scripts that will take away a bit of the work .

[barrycarlyon]

Ut oh, someone mentioned Dreamweaver, (starts hunting with rifle)

We all know real coders do not use Dreamwearer.

That is all.

[igorw]

It can in fact be pretty powerful if you know how to use it. A good coder should also be able to do something in dreamweaver.

[barrycarlyon]

Notepad or edit pad pro, or notepad++ just not dreamweaver.

[momentum]

Although I share your dislike for Dreamweaver, once you manage to turn off all the crappy things it can do to HTML it can be quite powerful. Unfortunately it's aimed at web "artists" who really don't want to know the tech side (read: they're ignorant) and really don't care how much bloat their sites carry.

Craig.

[barrycarlyon]

Agreed!

[igorw]

Sorry to interupt you guys, but this topic is really not about text editors.

[Mighty Gorgon]

I love this change.

I also did something similar in a modded phpBB 2 by also assigning page names to a constant.

I.E.:

Code: Select all

define(PAGE_INDEX, 'index.' . $phpEx);

By assigning these for each main page and by editing all the callback to the files, I was able to name all the files as I wish without having to change all the code everytime.

As you said the most important thing is that CONSTANTS are more secure, and you do not need to declare them as GLOBAL when you need to recall within functions or classes.

Thanks for the info.

[Obsidian]

In my opinion, phpBB3 needs a page based constant by default, especially if a styler wants to make an 'activetab' wannabe tab system in the overall header, so that tab X is highlighted when on page X, or if a MOD author puts some queries into the common code but have it hardcoded not to run when in the UCP, ACP, etc. to cut down on loads of edits to many different files.

[igorw]

There is the {SCRIPT_NAME} template variable you can use for that.