It would probably know better where the end of the line is will easily be done, than having it go through more work finding out how to do it for colons or semi-colons. So that is final? No on the colons and semi-colons.
Offline
say var & say "text" &
Those are ampersands at the end of each line.
(Shift + 7)
Maybe at the beginning and end of the script...
begin say "testing. testing. 123. testing" & end
Offline
end of line is a special character represented by "\n".
idk what's with the mood.var or var.mood thing though. Oh wait. why need other variable for answer, I mean, if we're not doing it like
answer = ask("question")
, then why bother with
ask("question", answer, yes)
thing? I mean, we can just make a global, built-in variable "answer", containing the last question's answer.
Offline
Does anyone consider my thing?
ask('whatever') answer = ask('whatever')
We just need to parse it...
Filo5, I think it's better to just have more variables, because it already is confusing in Scratch.
Offline
Gersh: We don't want it more complicated than possible, we want this as simple for us and who uses Emerald.
Filo: "answer" is and will be a default variable. This is going to be as much like Scratch as possible.
Dane: What do you mean?
Offline
Magnie wrote:
1. Gersh: We don't want it more complicated than possible, we want this as simple for us and who uses Emerald.
2. Filo: "answer" is and will be a default variable. This is going to be as much like Scratch as possible.
3. Dane: What do you mean?
1. I was just thinking of a way to end lines without colons OR semicolons
2. Good.
3. Asking the same thing.
Offline
Greatdane wrote:
Does anyone consider my thing?
Code:
ask('whatever') answer = ask('whatever')We just need to parse it...
Filo5, I think it's better to just have more variables, because it already is confusing in Scratch.
If you get confused with variables, then lets have less and as Filo said, a global variable called Answer. Saves confusion, and makes it more like scratch, as we're aiming for.
Offline
Well, if you actually need to have multiple answer variables, you have to do it by
ask
set var1 to answer
ask
set var2 to answer
So, in Emerald it's either
ask() var1 = answer ask() var2 = answer
or
var1 = ask() var2 = ask()
This would save lots of programming.
Offline
I made a little survey for you all to take. (includes non-Emerald team members, etc.)
http://spreadsheets.google.com/viewform?formkey=dE9FaWVCTjdSeW1xYklrb3ZOeUdaNnc6MA
It's about Emerald. It would really help if you took it.
Offline
Filo: We're making a Text-Based Version of Scratch, not are own language that we can implement whatever we want and make it as different from Scratch as possible, if you want to make your own programming language, then do it, but we need this as close to Scratch as possible.
Gersh: I'll go add the link to the main post, and the last question "Do you think this Survey was a waste of your time?" and I selected "Yes" xD
Last edited by Magnie (2009-12-05 22:41:54)
Offline
Um... yes. The thing is, Emerald will be a step between Scratch and other programming languages, right? So, why not start to interpolating them, like:
if < length(var1) == var2 >
{
i = 100
repeatFor < i <= var1 >
{
letter(var1,i) = element(list1,i)
}
say(var1,3s)
}
So it is similar both to Scratch and C# or Python!
Offline
filo5 wrote:
Um... yes. The thing is, Emerald will be a step between Scratch and other programming languages, right? So, why not start to interpolating them, like:
if < length(var1) == var2 >
{
i = 100
repeatFor < i <= var1 >
{
letter(var1,i) = element(list1,i)
}
say(var1,3s)
}
So it is similar both to Scratch and C# or Python!
Are we really need the {'s and }'s?
Id say keep it simple like in scratch, with block types bits of code, but they are indented for easy reading. Like in scratch.
Offline
Filo: For the last time, we are not making it harder for us, others, and me myself.
Magnie wrote:
We're making a Text-Based Version of Scratch, not are own language that we can implement whatever we want and make it as different from Scratch as possible, if you want to make your own programming language, then do it, but we need this as close to Scratch as possible.
Okay??
Offline
Magnie wrote:
Filo: For the last time, we are not making it harder for us, others, and me myself.
Magnie wrote:
We're making a Text-Based Version of Scratch, not are own language that we can implement whatever we want and make it as different from Scratch as possible, if you want to make your own programming language, then do it, but we need this as close to Scratch as possible.
Okay??
Though, will we take request for new features like the mesh and stuff?
Offline
Lol filo5 the only think you do on scratch, is posting on this thread. No posting on anywhere else, and no making projects.
Offline
Lucario621 wrote:
Lol filo5 the only think you do on scratch, is posting on this thread. No posting on anywhere else, and no making projects.
Off topic much?
And so... your point is...
Offline
gershmer wrote:
Lucario621 wrote:
Lol filo5 the only think you do on scratch, is posting on this thread. No posting on anywhere else, and no making projects.
Off topic much?
And so... your point is...
Well if he's only going to talk about stuff non-related to scratch, and just about other programming languages, then he should do it somewhere else.
Offline
Filo: I explained once, you asked again, and I explained again, it's not good to spam.
Offline
Magnie wrote:
Filo: I explained once, you asked again, and I explained again, it's not good to spam.
When was he spamming...?
o____O
Offline
By asking the same thing twice, or close to the same thing. ( I knew someone was going to ask. )
Offline
Magnie wrote:
By asking the same thing twice, or close to the same thing. ( I knew someone was going to ask. )
I see...
-______-
Offline
Magnie wrote:
The coding is done in a way that it doesn't matter how you type ANYTHING, any code, anything. So you could type 'AsK' or 'aSk' and it will still do the same.
Do you know that works for the ask block ALL the time? I've seen so many people say "this is case sensitive" but the ask block doesn't check for case sensitive. I've tested it out.
Offline
Magnie, I'm thinking of writing a help manual for Emerald.
But... should I write one for Emerald 0.3, Opal 0.3, wait for Emerald 0.4, or what?
Offline