Re: require/include a file inside a function [message #172705 is a reply to message #172690] |
Sat, 26 February 2011 18:35 |
Twayne
Messages: 135 Registered: September 2010
Karma:
|
Senior Member |
|
|
In news:ik88u3$3kj$2(at)news(dot)albasani(dot)net,
The Natural Philosopher <tnp(at)invalid(dot)invalid> typed:
:: Twayne wrote:
::: In
::: news:timstreater-63D4A7(dot)17074224022011(at)news(dot)individual(dot)net,
::: Tim Streater <timstreater(at)waitrose(dot)com> typed:
::::: In article <ik62hj$uep$1(at)news(dot)eternal-september(dot)org>,
::::: "Twayne" <nobody(at)devnull(dot)spamcop(dot)net> wrote:
:::
::: ...
:::
:::::
::::: You clowns gonna learn to *snip*, one of these
::::: centuries?
:::
::: My 2 B":
:::
:::
::: Actually, I'm rather happy to see the above comment, so
::: few people trim anything here, and a couple others who
::: even trim what they're responding to. Very few in this
::: particular set of groups seem to understand the snipping
::: process and how to do it. One in particular provides
::: great responses using the Reply feature, but then
::: snips everything but his own response. For those who
::: don't know: The generally most effective snipping is to
::: trim out what you are not resonding to, keep the part you
::: are responding to, and any supporting data such as OS,
::: apps, verstions, etc., and done so with inline posting
::: for clarity if it consists of more than a paragraph or
::: two.
:::
:::
:::
::
:: ..and then you get accused of responding out of context!
::
:: It is actually not as simple as it appears.
IMO the first rule is "When in Rome... ."
Finding no consensus in the existing posts, then the backup is the RFC
netiquette suggestions, in order of preference, Inline, Bottom Posted, and
Top Posted least preferred, and TRIMMED for relevance in any case, being
sure to leave spec-type info such as system descrips, RAM, et al that may be
relevant.
HTH,
Twayne`
|
|
|