Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

making a curses library

Name: Anonymous 2008-10-14 13:31

What level of competence do you think would be required to make a crappy curses library?

Name: Anonymous 2008-10-14 13:34

Understanding C and the concept of terminal control codes.  i.e. minimal.

Name: Anonymous 2008-10-14 13:37

>>1
How crappy? Any why not use one of the crappy curses libraries that already exist?

Name: Anonymous 2008-10-14 13:39

YOU
ARE
 A
FUC KIN G
IDIOT

Name: Anonymous 2008-10-14 18:04

>>1
Why? curses/ncurses already exist.

Name: Anonymous 2008-10-14 18:09

>>5
>>3

I fancy having a go at it.

Name: Anonymous 2008-10-14 18:48

>>6
yaranaika

Name: Anonymous 2008-10-14 18:51

>>6
Why?

Name: Anonymous 2008-10-14 19:27

>>8

Why not? Could be fun. I'm just wondering if I'm getting into something that I have no chance of finishing.

Name: Anonymous 2008-10-14 19:34

>>9
But why? Why would you do a bad rewrite of curses/ncurses/pdcurses? Why would you do such a thing?

Name: Anonymous 2008-10-14 20:13

>>9
THINK OF THE CHILDREN

Name: Anonymous 2008-10-14 20:18

>>10

Maybe I'll learn something?

Name: Anonymous 2008-10-14 20:21

>>12
Maybe you'll learn something doing anything else.

Name: Anonymous 2009-03-06 7:31

The X protocol Xlib.

Name: Anonymous 2009-07-21 3:16

>>1
love plugins i use usually NERD  to many NERD import Street, "b", "u", 02110-1301, i resonably lisp lisp get beginning for even still even sumOfFactors  sumOfFactors  factor programming FLOOD FLOOD FLOOD FLOOD penis penis penis penis penis delenda the as  but Someone should should been paid the dog. any  the Secondly, you  you Secondly,

Name: Anonymous 2010-11-27 5:06

Name: Anonymous 2011-02-04 12:53

Name: Anonymous 2011-02-04 14:13

Name: Anonymous 2011-10-11 14:30

var h;
You shouldn't allow unitialized variables in a language with type inference. That's calling for silly bugs.

    /* classes created with 'created' are allocated[o]
       on the heap, and are similar to the
       function-style initiation of classes
       in C++. They don't need to be explicitly
       deallocated. */[/o]I see what you're trying to do but this syntax is bad and there's no point in allocating those instances on the heap instead of the stack.

end;
Terrible!

        /* allocate, reallocate and deallocate are[o]
           keywords, and can be overloaded by
           defining 'func operator allocate(Object ob, int size)'
           for all types, or 'func operator allocate(<type> ob, int size)'
           for specific types.
           even in overloaded functions, the global
           standard 'allocate' family functions are
           accessible through 'Object.alloc', 'Object.realloc',
           and 'Object.dealloc'. */[/o]One doesn't allocate an object but space for it. I guess you're trying to make the use of memory pools more convenient and failing.

if typecasting is not possible, a Sys.Exceptions.TypeCastError' is thrown
An exception for a static cast makes no sense because it can be verified at compile-time. Be more clear, please.

Name: Anonymous 2011-10-11 14:32

var h;
You shouldn't allow unitialized variables in a language with type inference. That's calling for silly bugs.

    /* classes created with 'created' are allocated
       on the heap, and are similar to the
       function-style initiation of classes
       in C++. They don't need to be explicitly
       deallocated. */
I see what you're trying to do but this syntax is bad and there's no point in allocating those instances on the heap instead of the stack.

end;
Terrible!

        /* allocate, reallocate and deallocate are
           keywords, and can be overloaded by
           defining 'func operator allocate(Object ob, int size)'
           for all types, or 'func operator allocate(<type> ob, int size)'
           for specific types.
           even in overloaded functions, the global
           standard 'allocate' family functions are
           accessible through 'Object.alloc', 'Object.realloc',
           and 'Object.dealloc'. */
One doesn't allocate an object but space for it. I guess you're trying to make the use of memory pools more convenient and failing.

if typecasting is not possible, a Sys.Exceptions.TypeCastError' is thrown
An exception for a static cast makes no sense because it can be verified at compile-time. Be more clear, please.

Name: Anonymous 2011-10-11 14:33

var h;
You shouldn't allow unitialized variables in a language with type inference. That's calling for silly bugs.

    /* classes created with 'created' are allocated
       on the heap, and are similar to the
       function-style initiation of classes
       in C++. They don't need to be explicitly
       deallocated. */
I see what you're trying to do but this syntax is bad and there's no point in allocating those instances on the heap instead of the stack.

end;
Terrible!

        /* allocate, reallocate and deallocate are
           keywords, and can be overloaded by
           defining 'func operator allocate(Object ob, int size)'
           for all types, or 'func operator allocate(<type> ob, int size)'
           for specific types.
           even in overloaded functions, the global
           standard 'allocate' family functions are
           accessible through 'Object.alloc', 'Object.realloc',
           and 'Object.dealloc'. */
One doesn't allocate an object but space for it. I guess you're trying to make the use of memory pools more convenient and failing.

if typecasting is not possible, a Sys.Exceptions.TypeCastError' is thrown
An exception for a static cast error makes no sense because it can be verified at compile-time. Be more clear, please.

Don't change these.
Name: Email:
Entire Thread Thread List