L
Lasse Espeholt
Hi...
I am relativ new to the impressive and powerfull C language, but i
thinks it is obsolete...
The idea with header/source files where methods can clash into
eachother i don't like... Look at C# which is much cleaner with
namespaces.
Why has C not namespaces and a "area idea" where some methods and
fields could be hidden from the outside?
Something like:
a_source_file.c:
namespace SomeName(.SomeName)
{
area Stack
{
private int[] myStack;
private void someMethod() {};
public void push(int i) {};
public int pop() {};
}
}
another_source_file.c:
using SomeName(.SomeName);
int main(int argc, char[] *argv)
{
Stack.push(10);
System.printf(Stack.pop());
}
I'm really annoyed
Is im the only own with that point of view?
If i was a really good programmer (which i'm not... yet!
) i would
developed a compiler and a much more simple (but still impressive and
powerfull) c...
Best and kindest regards
Lasse Espeholt
I am relativ new to the impressive and powerfull C language, but i
thinks it is obsolete...
The idea with header/source files where methods can clash into
eachother i don't like... Look at C# which is much cleaner with
namespaces.
Why has C not namespaces and a "area idea" where some methods and
fields could be hidden from the outside?
Something like:
a_source_file.c:
namespace SomeName(.SomeName)
{
area Stack
{
private int[] myStack;
private void someMethod() {};
public void push(int i) {};
public int pop() {};
}
}
another_source_file.c:
using SomeName(.SomeName);
int main(int argc, char[] *argv)
{
Stack.push(10);
System.printf(Stack.pop());
}
I'm really annoyed
If i was a really good programmer (which i'm not... yet!
developed a compiler and a much more simple (but still impressive and
powerfull) c...
Best and kindest regards
Lasse Espeholt