Elysian Shadows

tappatekie wrote:@The Floating Brain:
erm.. No idea why your post was deleted? but the answer is, I prefer having private members on top of public to basically say, these public functions use these private functions.

superLED wrote:

tappatekie wrote:@The Floating Brain:
erm.. No idea why your post was deleted? but the answer is, I prefer having private members on top of public to basically say, these public functions use these private functions.

But keep in mind that if you are working with other people, and they are going to use your code, they only need to see the public functions, because that's all they are going to use.
If you have a huge list of private stuff at the top, people would need to scroll down an look for the things they wanna use.

Private stuff is only(?) used within that class. Putting it at top and say "Look at this" is in my eyes not efficient.
But we all find our own way of dealing with things. If you find this easier to read and understand, go for it ^^

This method helps me. "Do I have a function to rotate and scale the text?" *Looking through the public functions* "Oh, yes, I have. And that's how I use it".

k1net1k wrote:Did I delete the wrong post from this thread ? If so, I apologise. Someone had marked the post as reported and the post said something like "I couldnt work out how to delete this" So I deleted it.

tappatekie wrote:@The Floating Brain:
erm.. No idea why your post was deleted?

tappatekie wrote: but the answer is, I prefer having private members on top of public to basically say, these public functions use these private functions.

class A
{
   private:
      int myInt;
      string s;
   public:
      void Func();
      void Func2();
}

class B
{
   private int myInt;
   private string s;
   public Func();
   public Func2();
}

THe Floating Brain wrote: I wasent questioning your style, I was questioning your syntax.

For example:

Code: Select all

class A
{
   private:
      int myInt;
      string s;
   public:
      void Func();
      void Func2();
}

As opposed to:

Code: Select all

class B
{
   private int myInt;
   private string s;
   public Func();
   public Func2();
}

def i = 0
method printTheIDef(o,j,a) { 
      printl("Your arguments where" & o & j * a)
      printl(i)
}

def i = 0
i = array() { "Lol", "I was an integer...", "But now...", "I am an array?" }

tappatekie wrote:

THe Floating Brain wrote: I wasent questioning your style, I was questioning your syntax.

For example:

Code: Select all

class A
{
   private:
      int myInt;
      string s;
   public:
      void Func();
      void Func2();
}

As opposed to:

Code: Select all

class B
{
   private int myInt;
   private string s;
   public Func();
   public Func2();
}

The programming language (Plywood) does not actually have classes... or accessors to methods

It's more like

Code: Select all

def i = 0
method printTheIDef(o,j,a) { 
      printl("Your arguments where" & o & j * a)
      printl(i)
}

A method (as well as every definition) can have ANY value type passed to it. So there is no need for int i = 0, the interpreter does that for you.

So I can do fancy stuff like

Code: Select all

def i = 0
i = array() { "Lol", "I was an integer...", "But now...", "I am an array?" }

I made it like this because it makes your code less cluttered (in my opinion) and it looks more cleaner (in my opinion again)..

But... if you mean how I use my c# syntax, it's the second one...

THe Floating Brain wrote:

tappatekie wrote:

THe Floating Brain wrote: Im kinda confused at first I though it was Plywood then C# then Plywood now I think its C#.

superLED wrote:But keep in mind that if you are working with other people, and they are going to use your code, they only need to see the public functions, because that's all they are going to use.
If you have a huge list of private stuff at the top, people would need to scroll down an look for the things they wanna use.

tappatekie wrote: Every teaser from now has been in C# from Visual Studio...
Every code block in my posts is plywood syntax

Also, what you mean by nice dynamic typing?

dandymcgee wrote:

superLED wrote:But keep in mind that if you are working with other people, and they are going to use your code, they only need to see the public functions, because that's all they are going to use.
If you have a huge list of private stuff at the top, people would need to scroll down an look for the things they wanna use.

I prefer private at the top in C++, as it's the way I learned. I like to see my variables before I see my functions. In C# I don't generally sort by private / public, but rather group things however makes the best sense. First of all, I'm worried about maintainability and readability for myself above some random person who's not familiar with the code base. Second, Visual Studio's Intellisense almost entirely does away with the need for higher level users to go into my code. Third, even without Intellisense I would still favor personal readability and solid documentation over writing undocumented code that idiots can easily read because they see public first.

THe Floating Brain wrote: Dynamic Typing: the ability to change the data-type of variables (I believe), like in Python or Lua.

bbguimaraes wrote:On the code organization topic: reading source code should be the last resource when trying to understand how some part of the application works. You (the developer) should supply documentation to guide users (developers using your code, not the end user).

tappatekie wrote:

bbguimaraes wrote:On the code organization topic: reading source code should be the last resource when trying to understand how some part of the application works. You (the developer) should supply documentation to guide users (developers using your code, not the end user).

I haven't decided yet whether I open source it, however there is advantages, the programming language internal systems cannot be touched by other people since its a little security issue (unless I make it a seperate library..)