sorry for starting many threads but soon i will go away for some months
i guess so the group will be get rid of my threads - and until i am
i dont like to ged bored if i code something so i prefer to
start many threads just for fun and with no big reason
here such thread is write code for RLE (run length encoding)
then i cpuld eventualy compare it how i would write it -
it shouldnt be hard task but may be good to compare style
of coding or something (i will probbaly write it a bit later and post
it, but dont know yet know when)
fir wrote:
sorry for starting many threads but soon i will go away for some months
i guess so the group will be get rid of my threads - and until i am
i dont like to ged bored if i code something so i prefer to
start many threads just for fun and with no big reason
here such thread is write code for RLE (run length encoding)
then i cpuld eventualy compare it how i would write it -
it shouldnt be hard task but may be good to compare style
of coding or something (i will probbaly write it a bit later and post
it, but dont know yet know when)
note lek beack tehen years ago when i was learning programming
i noted and somewhat took teh opinion that this RLE is lame
but thinking today its not necessary such lame, simple and basic
doesnt necessary means lame imo
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 919 |
Nodes: | 10 (1 / 9) |
Uptime: | 47:12:00 |
Calls: | 12,183 |
Calls today: | 3 |
Files: | 186,524 |
Messages: | 2,236,092 |