|
PureBytes Links
Trading Reference Links
|
Hello,
Barry Scarborough wrote:
>> A compiler that found all the errors, listed them at the
> > bottom with what the error definition is and allowing me to click on
> > that line and be taken to the error line would be much better, but
> > now we are talking about the diagnostic ability of a MS Visual C++
> > compiler. I double we will ever get that. But improvement could be
> > made.
Exactly this is available now in newly released AmiBroker 4.68.2 BETA.
http://finance.groups.yahoo.com/group/amibroker-beta/message/1780
( To my surprise apparently no-one noticed )
Best regards,
Tomasz Janeczko
amibroker.com
> > ----- Original Message -----
> > From: "Barry Scarborough" <razzbarry@xxxx>
> > To: <amibroker@xxxxxxxxxxxxxxx>
> > Sent: Saturday, January 22, 2005 5:05 PM
> > Subject: [amibroker] Re: Training and/or User Groups
> >
> >
> >
> >
> > We need a comprehensive manual with well documented and coded
> > examples with comments on each line, the more the better. And we
> > need a compiler that locates the error and tells us what is
wrong.
> > Both of the current items fall short of what we need to write
> > effective code without pulling our hair out.
> >
> > I do not agree with using weekly subjects with examples within
the
> > context of the forum. Have you tried to locate articles on the
forum
> > using search arguments? It is almost impossible to find a
specific
> > topic and difficult at best to find what you are looking for. A
> > search returns many articles, then you have to browse through
them
> > spending huge amounts of time and often coming away more
frustrated
> > than when you began. Many of the example assume you already know
how
> > to program within AB, bad assumption, and they are not commented
> > well at all. The more terse the example the more difficult they
are
> > to follow. You can, and some often do, pack a lot of code on one
> > line and unless you understand the language and have a block
comment
> > above the code telling you what is being done in human language,
you
> > will not follow what is being done. Examples should not do this.
> >
> > An online manual or a newer version in PDF that allows searches
> > would be good. How-to subjects with examples would be much better
> > than the manual we now have. The manual we now have often
provides
> > links to examples on their website but they are not commented
well
> > and many times are terse and very difficult for a newbie or even
a
> > programmer to understand. Finding exactly what you are looking
for
> > is very difficult. But that is what the forum is for. If the same
> > question is asked over and over then it is a candidate for an
online
> > example withj comments. Examples should also have meaningful
> > variable names or good comments so they are easy to follow.
> >
> > Another thing that would really be helpful is a compiler that
placed
> > the cursor ON THE FAILING LINE with a good explanation of what
the
> > failure is. I often, especially when I am using for or if
> > statements, I find an error at the end of the code with the
cursor
> > on the last line of code and saying something like "Hey you
screwed
> > up. He he. See if you can figure out where you made a mistake."
Many
> > times I have had to comment out large blocks of code trying to
find
> > out where the problem is. Then it is not always obvious what the
> > error is. A compiler that found all the errors, listed them at
the
> > bottom with what the error definition is and allowing me to
click on
> > that line and be taken to the error line would be much better,
but
> > now we are talking about the diagnostic ability of a MS Visual
C++
> > compiler. I double we will ever get that. But improvement could
be
> > made.
> >
> > A comprehensive manual is what we need. Allowing users to provide
> > comprehensive well document examples would be great too. Put
them in
> > a library on the AB site, not in the forum.
> >
> > All the seminars I have attended, I am an IBM programmer and have
> > attended tons of them, addressed general topics, unless they are
> > weeks long. Newbies need a general, low level seminar to get
used to
> > the code. People who have a fairly good grasp of the language and
> > how to use it would require a more comprehensive seminar,
actually a
> > programming class that lasts a week or more. But when you walk
away
> > from a seminar you had better have a comprehensive manual because
> > you are not going to remember what you were taught in a month.
> > Typically you lose 80% to 90% of what you are taught in three
months
> > unless you start using it right away and keep at it. If you go
to a
> > seminar and try to use what you learned a year later, forget it.
You
> > will be looking in the manual.
> >
> > We also need a more comprehensive description of how to use the
> > Automatic Analysis tools, back tester especially. I have not
figuree
> > out how to use them effectively yet and I have been coding in AB
for
> > 1.5 years. Once again, how do you set the settings? I still don't
> > know how to set them for a real world experience.
> >
> > Barry
------------------------ Yahoo! Groups Sponsor --------------------~-->
In low income neighborhoods, 84% do not own computers.
At Network for Good, help bridge the Digital Divide!
http://us.click.yahoo.com/EpW3eD/3MnJAA/cosFAA/GHeqlB/TM
--------------------------------------------------------------------~->
Check AmiBroker web page at:
http://www.amibroker.com/
Check group FAQ at: http://groups.yahoo.com/group/amibroker/files/groupfaq.html
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/amibroker/
<*> To unsubscribe from this group, send an email to:
amibroker-unsubscribe@xxxxxxxxxxxxxxx
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|