Recently in C/C++ Category

Ich habe alle alten Versionen des yChats zusammengesucht (teilweise sind da Versionen dabei wo ich noch nicht wusste, dass es Versionskontrollsysteme gibt) und alle in das yChat Subversion Repository archiviert.

Erstaunlich was sich so angesammelt hat:

pb@earth:~/svn/ychat$ ls trunk/
ychat  ycurses  yhttpd
pb@earth:~/svn/ychat$ ls branches/
ychat-0.5  ychat-0.5-basic  ychat-0.7  ychat-0.8
pb@earth:~/svn/ychat$ ls tags/
ychat-0.1    ychat-0.5.5    ychat-0.7.7.0  ychat-0.8.0
ychat-0.2    ychat-0.6      ychat-0.7.7.1  ychat-0.8.1
ychat-0.3    ychat-0.7.0    ychat-0.7.8    ychat-0.8.2
ychat-0.4    ychat-0.7.1    ychat-0.7.9.0  ychat-perl-legacy
ychat-0.5.0  ychat-0.7.2    ychat-0.7.9.1  yhttpd-0.7.0
ychat-0.5.1  ychat-0.7.3    ychat-0.7.9.2  yhttpd-0.7.1
ychat-0.5.2  ychat-0.7.4.1  ychat-0.7.9.3  yhttpd-0.7.2
ychat-0.5.3  ychat-0.7.5    ychat-0.7.9.4
ychat-0.5.4  ychat-0.7.6    ychat-0.7.9.5
pb@earth:~/svn/ychat$ ls tags/ychat-perl-legacy/
0.2.1   0.2.4c   0.4.1    0.4.5a   0.4.9  0.7.1  0.8.1
0.2.2   0.2.5a2  0.4.2    0.4.6    0.6.0  0.7.2
0.2.3   0.2.6a   0.4.3a   0.4.7a2  0.6.1  0.7.6
0.2.4a  0.4.0a   0.4.4a3  0.4.8a2  0.6.2  0.8.0

Neben yChat habe ich dies auch mit den Schwesterprojekten yhttpd (HTTPD-Core des yChats) und ycurses (C++ Wrapper um ncurses in yChat und yhttpd zu benutzen) getan.

An yChat habe ich bereits ~5 Jahre nicht mehr gearbeitet. Dementsprechend sollte man die Software auch nicht mehr einsetzen. Ich weiss nichteinmal, ob sie sich überhaupt noch kompilieren lässt. Allerdings ist es immer mal wieder schön in der Vergangenheit zu kramen

Ein Klassiker der Referenzen der Programmiersprache C++ ist die Website www.cppreference.com. Die Site ist immer Empfehlenswert (gerade da sie relativ übersichtlich gestaltet ist und man sich relativ schnell zurecht findet). Fragen betreffend C++ im IRC kann ich meist (seit mehreren Jahren) mit einem Verweis darauf beantworten. :)

After reading Structure and Interpretation of Computer Programs I decided to rethink the interpreter of Fype. Fype is a small scripting language invented and implemented (in C) by me. I decided to take the code-base of Fype and to rewrite the core of its interpreter-part in order to use a Scheme/Lisp-like syntax. which is much easier to parse. The syntax is simpler and much more powerful now. So far it is now possible to define functions and sub-functions and to display all involving frames. Here is an example:

(def (test)
   (say "This is test")
   (def (test2) 
      (say "I am in test2" "And test3 will be defined next!")
      (def (test3)
         (say "Displaying all frames now:")
         (show-frames))
      (test3))
   (test2))
(test)

The invocation of the interpreter prints out the following result:

This is test
I am in test2
And test3 will be defined next!
Displaying all frames now:
FRAME(id=3) 0:
FRAME(id=2) 1:
+ST_LAMBDA(name=test3;args=)
( ( say Displaying all frames now: ) ( show-frames ) )
FRAME(id=1) 2:
+ST_LAMBDA(name=test2;args=)
( ( say I am in test2 And test3 will be defined next! ) ( def ( test3 ) ( say Displaying all frames now: ) ( show-frames ) ) ( test3 ) )
FRAME(id=0) 3:
+ST_LAMBDA(name=test;args=)
( ( say This is test ) ( def ( test2 ) ( say I am in test2 And test3 will be defined next! ) ( def ( test3 ) ( say Displaying all frames now: ) ( show-frames ) ) ( test3 ) ) ( test2 ) )

Now what's left to do: Implement a few more built in functions. And we have a new Scheme/Lisp-like language with a very very small footprint available :)

Btw.: This version of fype aims to be pure-functional and with lazy evaluation.

No, this is not going to be a Windows cetric blog. But I want to mention, that I hate Windows and Windows hates me!

For $money I developed a TCP/IP server application in C which should run in background (without having a DOS window in the foreground). It would have been so easy if it'd be like on almost all other operating systems: nohup ./yourprogram &

On Windows XP you need to extend your C application in order to support Windows Services. In order to support Windows Services, you need to write about 50 more LOC. And it is frustrating to find out how to change the working directory of your own Windows Service. The standard working directory is c:\WINDOWS\system32. I managed doing so in reading an optional parameter (which is editable in the Windows Registry [uargh, why not under the Windows Service options?]) and to use the SetCurrentDirectory function of the WinAPI. Whah, yet another nasty thing about Windows: The function name SetCurrentDirectory starts with a capital letter, which is against my own coding conventions ;)

After all, everything is now running as expected! And without Cygwin it almost would have been mission impossible!

I do not like Windows ;)

Use the following Code in your Makefile and use "make style" and get your C code formatted.  It will also prove that no  source line is longer than 80 chars. It will print a notice if more than 80 chars per line are reached and it will also print the affected filenames and line numbers. This script needs to have astyle installed and it has been tested on FreeBSD with pmake but not with GNU Make. You may need to modify the script if you are going to use Linux w/ GNU Make.

 style: astyle check
 astyle:
     find ./src -name '*.[ch]' -exec sh -c 'astyle -s3 {}; rm -f {}.orig' \;
 check:
     for f in `find ./src -name '*.[ch]'`; do awk -v f=$$f \
         '{ if (length($$0) > 80) { \
         printf "Max line length reached @ %s:%d => %d\n", \
         f, NR, length($$0) } }' $$f; done

Do you know days you only spend time debugging code and learning more and more advanced stuff like how to debug code (e.g. w/ GDB)? After starting implementing arrays in Fype I somehow screwed up the garbage collector. After fixing the GC I broke somehow scope.c (which is used to handle scopeing of variables within Fype scripts). After ~2 days of debugging I rolled back from revision 207 to 202 (now revision 208) and I'll start implementing arrays new from scratch. Probably I first should implement reference variables first in Fype. Array elements should be always references. Those should be handled differently by the GC.

Here is a mega screenshot of my new configured Xinerama (TwinView) desktop using a total screen resolution of 3520x1200 (1600x1200 CRT + 1920x1200 TFT). The X Window System is running the FVWM2-devel as its window manager. I am using xcompmgr for transparent windows and window shadows. The GVim editor is using a C function browser plugin, as well as code omni completion, tabbing, split screening, code navigation etc.! And it is running on FreeBSD 7.0-RC2 :) Btw.: This is how it looks like if I program on Fype!

Update: Embedded screenshot perview into this post