1. RE: Live Tutorial
don cole wrote:
>
> One more thing the code that Jason Gade sent you, input() will handle
> long
> strings like Qbasic's INPUT whare as my code only handles one chr at a
> time.
>
I don't like BASIC's Input, which is why I wrote all mine own custom
input routines in the first place. {Giggles} Nor did I like BASIC's
PRINT statement in it's plain-Jane incarnation, so I customized that as
well. {Laughs} The resulting cusomizations only output - and printed -
strings. So all the data that users input were strings and all that was
printed on the screen was strings. The subroutines were customized for
various applications, and specialized for Database Apps - something I
seem to be rather good at. {Blushing} So anything that allowed just any
old data to be input wasn't good enough. And INPUT was worse because it
had the Redo from start error which could really mess up a nicely
formatted computer screen. Not to mention it's permissiveness with the
arrow keys and stuff.
What I'm endeavoring to do now is to understand Euphoria enough to
compose my own input routines. The code snippets I have seen {outside
yours, of course, which are still very confusing to me} have all shown a
little bit of how to do this, but my first endeavors have pretty
consistently failed {Points to Error Report}.
I *can* see where you're trying to take it, however, and you are just as
clumsy as I am at tutoring. This isn't a bad thing, really. You are
quite skilled and very much love the language, and it shows. It's just
like me, you expect a person to understand much more then they often do,
and so, like me, you often go over the heads of others. I've said
things that were perfectly clear to me and watched people's faces screw
up in intense concentration as they tried to understand what I just
said. It's all rather embarassing, really. To make affairs more
confusing, traditional teaching methods and documentations tend to be
useless to me. I learned BASIC from what was essentially a BASIC
dictionary. I'm learning HTML essentially the same way {See
www.html-reference.com}. As far as I can tell, there is no Euphoria
Dictionary anywhere. Even if there was one, with the way you talk about
fixing standardized include files, I doubt it could ever really be
complete. So no one ever completely understands Euphoria, just as no
one ever completely understands C, and there's no way to actually
compose a complete and thorough dictionary on Euphoria, and no one's
going to take the time to create such a dictionary for each include file
they write or rewrite. So, my usual method is SOL. Hence, I am stuck
spamming you with questions on even the most basic things because
there's no Error Dictionary, and no Dictionary pointing out things that
I may be doing wrong, and no Dictionary on Euphoria that I can readily
find.
Even EE doesn't come with this kind of thing. It has some kind of
manual that it opens for editing. Immense help to someone like me,
that, when http://www.html-reference.com/ has taught me so much about
html in less than a week's time.
> I would also point out that a string always = sequence but a sequence
> does not always = a string.(Again see Gay's tutorial)
>
This makes perfect sense. A sequence could be a simple array of
numbers, and this is apparently how the program is choosing to handle my
"string" when I try to send it to the subroutine for printing.
>
> I know this might be a bit much but I hope it helps.
> I like your idea of sticking with Dos for now.
> That what I did when I first started w/Euphoria.
>
{Smiles} Staying with DOS is just easier and makes it closer to QBasic
for the time being. I've no need to make things any more complicated
than they need to be right now.
I think you're a great person. I will look over your code in detail
later. I rather enjoy people who like to talk over my head. The
challenge for me is to get up the knowledge where we can actually
understand each other. I usually feel very good about myself when I've
accomplished that.
Love & Friendship & Blessed Be!
Lynn Erika Kilroy
2. RE: Live Tutorial
Lynn Kilroy wrote:
<snip>
>
> I think you're a great person. I will look over your code in detail
> later. I rather enjoy people who like to talk over my head. The
> challenge for me is to get up the knowledge where we can actually
> understand each other.
<snip>
I think if actually *ran* the code (it has been tested) it would be a lot
clearer.
Don Cole
A Bug is an un-documented feature.
A Feature is a documented Bug.
3. RE: Live Tutorial
Lynn Kilroy wrote:
> I *can* see where you're trying to take it, however, and you are just as
> clumsy as I am at tutoring. This isn't a bad thing, really. You are
> quite skilled and very much love the language, and it shows. It's just
> like me, you expect a person to understand much more then they often do,
> and so, like me, you often go over the heads of others. I've said
> things that were perfectly clear to me and watched people's faces screw
> up in intense concentration as they tried to understand what I just
> said. It's all rather embarassing, really. To make affairs more
> confusing, traditional teaching methods and documentations tend to be
> useless to me. I learned BASIC from what was essentially a BASIC
> dictionary. I'm learning HTML essentially the same way {See
> www.html-reference.com}. As far as I can tell, there is no Euphoria
> Dictionary anywhere. Even if there was one, with the way you talk about
> fixing standardized include files, I doubt it could ever really be
> complete. So no one ever completely understands Euphoria, just as no
> one ever completely understands C, and there's no way to actually
> compose a complete and thorough dictionary on Euphoria, and no one's
> going to take the time to create such a dictionary for each include file
> they write or rewrite. So, my usual method is SOL. Hence, I am stuck
> spamming you with questions on even the most basic things because
> there's no Error Dictionary, and no Dictionary pointing out things that
> I may be doing wrong, and no Dictionary on Euphoria that I can readily
> find.
>
Well, did you take a look at the Language Definition
(http://www.rapideuphoria.com/refman_2.htm) and the Library Routines section
(http://www.rapideuphoria.com/library.htm) in the manual? I think it contains
what you want.
Regards, Alexander Toresson
4. RE: Live Tutorial
Lynn Kilroy wrote:
>
>
> What I'm endeavoring to do now is to understand Euphoria enough to
> compose my own input routines. The code snippets I have seen {outside
> yours, of course, which are still very confusing to me} have all shown a
> little bit of how to do this, but my first endeavors have pretty
> consistently failed {Points to Error Report}.
>
Have you taken a look at prompt_number() and prompt_string()?
http://www.rapideuphoria.com/lib_p_r.htm#prompt_number
http://www.rapideuphoria.com/lib_p_r.htm#prompt_string
> As far as I can tell, there is no Euphoria
> Dictionary anywhere. Even if there was one, with the way you talk about
> fixing standardized include files, I doubt it could ever really be
> complete. So no one ever completely understands Euphoria, just as no
> one ever completely understands C, and there's no way to actually
> compose a complete and thorough dictionary on Euphoria, and no one's
> going to take the time to create such a dictionary for each include file
> they write or rewrite. So, my usual method is SOL. Hence, I am stuck
> spamming you with questions on even the most basic things because
> there's no Error Dictionary, and no Dictionary pointing out things that
> I may be doing wrong, and no Dictionary on Euphoria that I can readily
> find.
>
I think you're confusing "Euphoria" the language with all of its libraries.
It's true that no one completely understands all of the code that various
users have created. But the language itself is actually very simple.
Also, asking questions on this list about Euphoria is definitely *not*
spamming. There will almost always be at least one person around who will
get back to you quickly with a helpful reply. It's a pretty good and
helpful community.
Matt Lewis
5. RE: Live Tutorial
Alexander Toresson wrote:
>
> Well, did you take a look at the Language Definition
> (http://www.rapideuphoria.com/refman_2.htm) and the Library Routines
> section (http://www.rapideuphoria.com/library.htm) in the manual? I
> think it contains what you want.
>
> Regards, Alexander Toresson
I know! I know! It's all there. I just had to understand enough of
the language to be able to understand what was in the docs. I'm so
sorry, but this is just how I work.
I look forward to rewriting my ColorLocateInputJustAboutAnything
function. It's looking like it will be a miniature text editor anyone
can plug in to any program. Since it's stuck with DOS, however, I will
probably have to modify / rewrite it for Windows.
What is 2 ^ 28, anyway?
Nevermind. I just asked Calc. It says that
ColorLocateInputJustAboutAnything will be able to address up to 56,000
pages of information. That's a lot of data! Fortunately, it's also
completely configurable. You have have it maxx out at just a few
characters or you can let it perform it's full editing capabilities in
all it's wonderous glory.
This will be fun.
Love & Friendship & Blessed Be!
Lynn Erika Kilroy
6. RE: Live Tutorial
don cole wrote:
>
> I think if actually *ran* the code (it has been tested) it would be a
> lot
> clearer.
>
Perhaps. But I think I've a pretty good grasp on what I'm doing, now.
I've learned what some of the errors mean and am taking wild guesses as
to what's cuasing them, and coming up with the correct answer more and
more. Euphoria is pretty easy. I still don't like functions, but since
functions are the only way to change a variable, then I'll live with
them. I have to call a function with a variable on both sides in some
cases ...
Variable = Function (Variable)
... which is a little odd to me, but I can live with it. But at least I
can code it ...
Variable =
Function (Variable)
... which I kind of like. Also, more complex functions tend to have
gobs and gobs and gobs of arguments. It's really nice to be able to ...
Variable =
Function (
Argument,
Argument0,
Argument1,
...
FinalArgument
)
It makes things really clear to me. Perhaps you would disagree.
Love & Friendship & Blessed Be!
Lynn Erika Kilroy
