"Wrong Expression" - EasyLanguage Programming | futures io social day trading
futures io futures trading


"Wrong Expression"
Updated: Views / Replies:599 / 3
Created: by deltastrike Attachments:0

Welcome to futures io.

(If you already have an account, login at the top of the page)

futures io is the largest futures trading community on the planet, with over 100,000 members. At futures io, our goal has always been and always will be to create a friendly, positive, forward-thinking community where members can openly share and discuss everything the world of trading has to offer. The community is one of the friendliest you will find on any subject, with members going out of their way to help others. Some of the primary differences between futures io and other trading sites revolve around the standards of our community. Those standards include a code of conduct for our members, as well as extremely high standards that govern which partners we do business with, and which products or services we recommend to our members.

At futures io, our focus is on quality education. No hype, gimmicks, or secret sauce. The truth is: trading is hard. To succeed, you need to surround yourself with the right support system, educational content, and trading mentors – all of which you can find on futures io, utilizing our social trading environment.

With futures io, you can find honest trading reviews on brokers, trading rooms, indicator packages, trading strategies, and much more. Our trading review process is highly moderated to ensure that only genuine users are allowed, so you don’t need to worry about fake reviews.

We are fundamentally different than most other trading sites:
  • We are here to help. Just let us know what you need.
  • We work extremely hard to keep things positive in our community.
  • We do not tolerate rude behavior, trolling, or vendors advertising in posts.
  • We firmly believe in and encourage sharing. The holy grail is within you, we can help you find it.
  • We expect our members to participate and become a part of the community. Help yourself by helping others.

You'll need to register in order to view the content of the threads and start contributing to our community.  It's free and simple.

-- Big Mike, Site Administrator

Reply
 
Thread Tools Search this Thread
 

"Wrong Expression"

  #1 (permalink)
Elite Member
California
 
Futures Experience: Intermediate
Platform: Multicharts
Favorite Futures: Futures
 
Posts: 6 since Mar 2012
Thanks: 5 given, 0 received

"Wrong Expression"

Hello master EL programmers...I've been dove into EL head first without a programming background and I'm trying to troubleshoot this code that I came across for a simple pattern signal. When I attempt to compile it it give me an error saying "wrong expression" and highlights the first "NumericSimple" input argument. I have no idea why this is wrong, it even looks identical to the example provided in the editor dictionary.

{#function C_3WhSolds_3BlkCrows}

Inputs:
Length(NumericSimple),
Percent(NumericSimple),
o3WhiteSoldiers( numericref ),
o3BlackCrows( numericref ) ;

variables:
BodyHi( 0 ),
BodyLo( 0 ),
Body( 0 ),
BodyAvg( 0 ),
UpShadow( 0 ),
DnShadow( 0 ),
MyRange( 0 ),
Factor( Percent * .01 ) ;

BodyHi = MaxList( Close, Open ) ;
BodyLo = MinList( Close, Open ) ;
Body = BodyHi - BodyLo ;
BodyAvg = XAverage( Body, Length ) ;
UpShadow = High - BodyHi ;
DnShadow = BodyLo - Low ;
MyRange = High - Low ;

o3WhiteSoldiers = 0 ;
o3BlackCrows = 0 ;

if CurrentBar > 2
and Body > BodyAvg
and Body[1] > BodyAvg[1]
and Body[2] > BodyAvg[2]
{ THREE CONSECUTIVE LONG BODIES }
then
begin
if Close > Open
and Close[1] > Open[1]
and Close[2] > Open[2]
{ ALL THREE BODIES WHITE... }
and Close > Close[1]
and Close[1] > Close[2]
{ ...EACH WITH A HIGHER CLOSE }
and Open < Close[1] and Open > Open[1]
and Open[1] < Close[2] and Open[1] > Open[2]
{ EACH OPEN WITHIN PREVIOUS BODY... }
and UpShadow / MyRange < Factor
and UpShadow[1] / MyRange[1] < Factor
and UpShadow[2] / MyRange[2] < Factor
{ ...AND EACH CLOSE NEAR HIGH }
then
o3WhiteSoldiers = 1
else if Close < Open
and Close[1] < Open[1]
and Close[2] < Open[2]
{ ALL THREE BODIES BLACK... }
and Close < Close[1]
and Close[1] < Close[2]
{ ...EACH WITH A LOWER CLOSE }
and Open > Close[1] and Open < Open[1]
and Open[1] > Close[2] and Open[1] < Open[2]
{ EACH OPEN WITHIN PREVIOUS BODY... }
and DnShadow / MyRange < Factor
and DnShadow[1] / MyRange[1] < Factor
and DnShadow[2] / MyRange[2] < Factor
{ ...AND EACH CLOSE NEAR LOW }
then
o3BlackCrows = 1 ;
end ;


Any help would be appreciated!

Reply With Quote
 
  #2 (permalink)
Quick Summary
Quick Summary Post

Quick Summary is created and edited by users like you... Add FAQ's, Links and other Relevant Information by clicking the edit button in the lower right hand corner of this message.

 
  #3 (permalink)
Elite Member
Texas, USA
 
Futures Experience: Advanced
Platform: X_TRADER Pro, Custom
Broker/Data: NxCore
Favorite Futures: Futures, Spreads
 
Hulk's Avatar
 
Posts: 222 since May 2014
Thanks: 529 given, 487 received



deltastrike View Post
Hello master EL programmers...I've been dove into EL head first without a programming background and I'm trying to troubleshoot this code that I came across for a simple pattern signal. When I attempt to compile it it give me an error saying "wrong expression" and highlights the first "NumericSimple" input argument. I have no idea why this is wrong, it even looks identical to the example provided in the editor dictionary.

...

Any help would be appreciated!

Just taking a shot here... Did you copy and paste this to create a new "Indicator" or a new "Function"? I am willing to bet that you mistakenly created an indicator instead of a function. The input types NumericSimple, NumericSeries etc are reserved words for functions and will fail to compile when used in anything other than a function.

Reply With Quote
The following user says Thank You to Hulk for this post:
 
  #4 (permalink)
Elite Member
California
 
Futures Experience: Intermediate
Platform: Multicharts
Favorite Futures: Futures
 
Posts: 6 since Mar 2012
Thanks: 5 given, 0 received


Hulk View Post
Just taking a shot here... Did you copy and paste this to create a new "Indicator" or a new "Function"? I am willing to bet that you mistakenly created an indicator instead of a function. The input types NumericSimple, NumericSeries etc are reserved words for functions and will fail to compile when used in anything other than a function.

Thanks!

Reply With Quote

Reply



futures io > > > > > "Wrong Expression"

Thread Tools Search this Thread
Search this Thread:

Advanced Search



Upcoming Webinars and Events (4:30PM ET unless noted)
 

Journal Challenge w/Earn2Trade and $599 in Prizes

November
 

Anthony Drager: TBA

Nov 29
 

Linda Raschke: TBA

Elite only
 

Peter Davies: TBA

Dec 6
 

Brannigan Barrett: TBA

Elite only
 

Cannon Trading: Ask Me Anything

Dec 13
     

Similar Threads
Thread Thread Starter Forum Replies Last Post
Why using the term "curve-fitting" is wrong Outlier Traders Hideout 1 January 21st, 2013 05:47 PM
Fukushima: "China Syndrome Is Inevitable" ... "Huge Steam Explosions", or "Nuclear Bo Quick Summary News and Current Events 0 November 22nd, 2011 02:50 AM
How to change "Stop Loss" and "Take Profit" in "shElderImpulse" Strategy javed759 NinjaTrader 1 November 1st, 2011 11:44 PM
"mid", "buy", "sell" volumes lokgotkent Traders Hideout 6 September 30th, 2011 02:24 PM
Warren Buffet is "wrong" on taxes RM99 News and Current Events 4 July 29th, 2011 11:10 AM


Tags
code, easylanguage, indicator, indicators, information, multicharts, neoticker, patterns, programming, signal, tradestation, xaverage

All times are GMT -4. The time now is 03:38 PM. (this page content is cached, log in for real-time version)

Copyright © 2018 by futures io, s.a., Av Ricardo J. Alfaro, Century Tower, Panama, +507 833-9432, info@futures.io
All information is for educational use only and is not investment advice.
There is a substantial risk of loss in trading commodity futures, stocks, options and foreign exchange products. Past performance is not indicative of future results.
no new posts
Page generated 2018-11-20 in 0.12 seconds with 14 queries on phoenix