Fri, 29 Jan 2016 08:19:14 +0000 Nicholas Marriott > Firstly, I don't think we need this in base and I think there is little > to no chance of it being taken, even if the code is improved.
Many folks tried this part (advising Luke), he takes none and keeps repeating wrong concepts, his assignment looks misaligned somewhat. > Secondly: > > - The code is still miles off style(9) and isn't really a consistent > style within itself either. This comes from an apprentice wannabe, probably best to recommend him further self help. > - Forking uname(1)? What? No offence, but that is hilarious :-). Why > fork uname(1) for uname(3) but not date(1) for gettimeofday(2)? The kid knows nothing of UNIX, ask him book reading comprehension questions in private please. > - Why would you fork sed either? Hint: suggest another list@ > I think C is the wrong tool for this. Why not write a shell, perl, or > python script? C is the wrong tool for that person, knows nothing of shell too. So best pick learning shell first. Typical, but never hopeless (still)? > Then if people start to use it you could make a port. Without thought at design stage, barely usable for private learning projects homework. The result is reiterations on misc@ where ideas spark in developer heads after some kid starts asking noisily without listening or prior knowledge.
