> I have found ways to work around these (setting everything up so that is
> assumes files are php files if it doesn't know what they are) but it's not
> the best solution since it kinda messes other things up.
I believe nedit (which is a Linux editor) recognizes file type by looking at
the first 1K of the file. If it sees <?php, it assumes it's a PHP file.
This
seems like the sensible approach.
> > Actually, I'm not sure this would work...consider that if you include a
> > file inside a function, those variables would be created inside the
> > function's scope.
>
> Hmm. I didn't know that. Couldn't the global variables be declared
global,
> and still be used?
No. You can't say "this variable here should be available globally".
Variables
declared inside a function are only available inside that function.
> Couldn't all the modules check for something that is defined in index.php?
> And this only relates to the first concern, which should really be solved
by
> making sure people understand how freetrade is meant to be installed.
It just seems like a lot of extra work to support having extensions.
> (btw: I *love* syntax highlighting! makes everything so clear, and
catches
> those stupid typing mistakes, like leaving out a quote mark. the way the
> program is built and it's flow just seems so much more obvious when
> everything is color-coded.)
I think this is just one of those things that I didn't have as I was
learning to program,
and I don't miss. But I do know lots of people love syntax highlighting.
Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Site: http://www.working-dogs.com/freetrade/
Problems?: [EMAIL PROTECTED]
