adam-lynch / ked Goto Github PK

I'm gonna hafta address da W3C bout dis boyee. Ya see dere is a spellin mistake in da grammer of da KED Lanwage!

'cmereToMeWilla' IS PLAIN WRONG, It shud be 'cmereToMeWillya'

Hurryup an fix it willya and don't u be givin me any lip about it eyether.

Perhaps fatal errors should be signalled with:

eh (condition)
{
ThisIsFec.ked like
}

From an email:

storyBhoy – used to get user input
yourSomeMog – used for debug assertions

Here lad, you've made a great start! Just a few thoughts:

1. Needs more 'boy'
2. Alias 'stallTheBeans()' for holdOn() - not sure if this is actually Cork or just some weird Ballincollig thing
3. isTheBopOff as 'extends' keyword for future OO features e.g class Tanora isTheBopOff SoftDrink
4. Define 'main' function as 'Pana'

Just the first few that came to mind. Sound!

1. Yeah, I know. It's hard to fit it in though.
2. Yep, will do.
3. How about isTheBopOffHisFather / isTheHeadOffHisFather? E.g. class Tanora isTheHeadOffHisFather FizzyDrink. I'll have to get a Tanora joke in there too, thanks.
4. Not sure about this one.

I'm going to add a list of contributors to the wiki (with your name in it) since not everyone will be contributing via actual pull-requests.

How can boy be fitted in? It's going to have to go in somewhere. Preferably something that might be used often, but it should make sense.

How to spell it? Bah? Bai? Bhoy? Biy? Or just leave it as "boy" since it's pronounced differently all over the gaff like?

Sure how do I write in me native tongue if there's no implementation, like

Error messages, pop-up notifications, etc

ahFFSLads(text)

I'm looking for a way that the master branch and gh-pages can be under the one branch so that both can be modified under a new fork/branch; i.e. when adding implementation for something, the documentation can be done in parallel on the same branch (therefore belonging to the same pull-request).

If anyone else could help me with this I'd be grateful. I found a way to manage them both under a grand-master branch when developing locally but that's not good enough.

Having to do something manual after each push to this repo (or merge in of a pull-request) is not what I'm looking for here.

Have you decided yet if you are going to have a type system or at least a primitives system?

Something like...
short == smallFella
long == lankyFella
string == focails

This isn't stricly speaking Cork, but shouldn't there be some kind of Father Ted reference in this?

Can't actually think of how we could fit in into the syntax, but maybe the interpreter could return an error message? Like invalid comparison could be "Okay Dougal, one last time. €x is number, but €y is string (or whatever alias we come up for string)."