|
PureBytes Links
Trading Reference Links
|
Pierre wrote:
"Again, read twice before posting to this list.
I know of what I speak, me.
You should also consider to subscribe to TS Express.
You will be pleased to see that I'm still the technical editor of Bill
Brower's journal.
Rather than to continue this discussion where you are losing battle after
battle..."
Once again -- that's about 20 times now -- Pierre you have missed the point.
My contention was that you nit picked my original 1 line function for stupid
things -- things which everybody agrees don't matter in functions like this.
You also made several incorrect assumptions which you didn't bother to
verify before submitting. One was the function was never intended to be
plotted. YOU SHOULD READ YOUR LETTERS TWICE. Such hypocracy is so typical
from your pontificatory camp.
I originally posted code to demonstrate how what Earl was talking about
could be done. The code was never the issue but you quickly made it one to
settle an old score. I was not attempting to document a CLEVER approach to
EL programming. This was an incorrect assumption. I was trying to show how
solving for a variable could be done. I provided EL code because it was the
easiest way to show the mathematical relationship.
But NO, you had to go and make it into code issue to try and demonstrate
just what a BIG guy you were. SO WHOSE THE ONE WITH THE EGO? No doubt you
have spent a great deal of time with EL as I have with my studies but please
make sure you HAVE THE POINT BEFORE YOU LEAP!!!! I KNOW THAT YOU PROBABLY
ONLY UNDERSTAND ABOUT 1/2 OF WHAT I WRITE DUE TO THE LANGUAGE BARRIER BUT
SHUOLD YOU REALLY CRITICIZE FOR SOMETHINGS YOU CAN"T FULLY UNDERSTAND?
I have actually been complimentary of your EL code in the past. Did you
forget this?
Clever programming isn't my style. I code to get it done and make sure that
it works reliably. If turns out to be elegant and clever great. If not so
what -- it still works and works reliably. I have more advanced EL code
(the iterative pivot point finder) and a lot of other stuff. I don't trade
systems so I don't write systems and I would never be so pretentious to say
I did.
Please Pierre, continue attempting to help people on this list. And I hope
they continue to buy your stuff.
But for everyone's sake and mine make sure you get the facts straight before
rushing off to repair your damaged ego and settle old scores.
Regards,
Brian.
-----Original Message-----
From: Orphelin@xxxxxxx [mailto:Orphelin@xxxxxxx]
Sent: Friday, November 13, 1998 7:07 AM
To: Omega BASHING List
Subject: Re: Easy Language Documentation?
Dans un courrier daté du 13/11/98 14:47:20 Heure d2iver Pari20 Madrid,
bnm03@xxxxxxx a écrit :
> Pierre wrote in response to Mark Brown:
>
> "If anyone has a secret book on EL , please let me know, but I seriously
> doubt that anything like this has been produced. Maybe some internal
help
paper
> for a basic support inside the company, I cant say."
>
> Ok, you're in detention mister. Class isn't dismissed. Once again you
stay
> true to form and have missed a vital fact about Extremely-Lame Language.
> There's a poop load of undocumented commands in EL that Omega has not
taken
> the time document. I keep running into them over the years but the ones
that
> come immdiately to mind are the Not only is what documentation that does
> exist a joke (which is why you have so many on this list clamoring for EL
> lessons but unable to distnguish a good lesson from a bad one) -- and
this
> is about the 6th revision of the TS Extremely-Lame Language manual -- but
> much of the added functionality
>
> #BeginAlert
> #End
> #BeginCmtry
> AtCommentaryBar
You should read the TS Readme file that comes with the software (available
from the Omega Research menu)
Maybe, as a seasoned programmer, you do not know that software editor put
there what is not available in the paper documentation?
Then you can read this:
#BEGINALERT Initiates alert procedure when alert condition
is
true.
#BEGINCMTRY Initiates commentary procedure when commentary
condition is true.
#BEGINCMTRYORALERT Initiates commentary or alert procedure
when either
commentary or alert condition is true.
#END Closes the alert or commentary procedure.
ATCOMMENTARYBAR See CHECKCOMMENTARY
CHECKCOMMENTARY Checks the status of commentary on a
bar-by-
bar basis for
real-time data, and
on the last bar of historical data.
There are dozens of examples in the Power Editor of all of these functions.
>
> No explanation about Strings or how to handle them (ie Concatenation).
If
> you're a seasoned basic programmer -- no sweat you already know this.
>
There are dozens of examples in the Power Editor of al of these function
too.
( concatenation).
See expert commentary studies for more.
> No explanation about using plot arrays (as in ADX) ex. plot1 > plot1[1].
> What the hell's this? Where is this in the book?
There are dozens of examples in the Power Editor of all of these
features;,mainly in their expert commentary examples.
It becomes obvious that plotX is treated and acting like variables do, e.g.
that you can refer to previous values.
>
> This is just what I could dredge up in the 3 minutes it took to write
this
> but is INDICATIVE OF THE CRAP AND FRUSTRATION I'VE EXPERIENCED OVER THE
> YEARS CODING IN THIS EXTREMELY-LAME LANGUAGE.
>
Again, read twice before posting to this list.
I know of what I speak, me.
You should also consider to subscribe to TS Express.
You will be pleased to see that I'm still the technical editor of Bill
Brower's journal.
Rather than to continue this discussion where you are losing battle after
battle...
> The King (we know the king!),
> Brian.
>
Hi hi...
Pierre Orphelin
|