hzhou321

20 ms·

151.
MyDef Manual(htmlpreview.github.io)
1 points by hzhou321 9y ago|0 comments
152.
by hzhou321 9y ago
Deng did it, not China. In fact, China do not care about constitution that much. The leaders do care, as always.
153.
by hzhou321 9y ago
The system never rotated.
154.
by hzhou321 9y ago
This is the norm for China, and it has worked (for its large part of world domination history), so nothing to hold your breath for. In that aspect, Deng Xiaoping was rather an anomaly (although his large part is still the norm). China prod
155.
by hzhou321 9y ago
The thing about language popularity is mostly about its ecosystem -- libraries, teachers, friends, and corporations behind them. However, all ecosystem are transient in nature, and all code that interwines and depends on a ecosystem will go
156.
by hzhou321 9y ago
> Delphi ... I just started picking up pascal again, freepascal to be specific. I started with pascal in school, quickly moved to C, then C++; As I gain experience and wisdom, I migrated back from C++ to C. I just discovered freepascal t
157.
by hzhou321 9y ago
I had the same sentiment as yours, but the blog is fine (for the author and appropriate audience). I am quite surprised/curious how it got to top page here.
158.
by hzhou321 9y ago
To clarify our views: The words and sentences are inside the file. The filenames are identifiers to the files. Identifiers' purpose is mainly to identify, rather than to communicate. On the other hand, we could imagine a user interface
159.
by hzhou321 9y ago
> There is nothing beneath the Windows UI interface. To clarify, beneath the GUI interface is the actual code that implements that interface. > Something working so well that it becomes an appliance isn't a bad thing. Not at all.
160.
by hzhou321 9y ago
> Almost every CLI program I've ever used in Windows has no problem with spaces in filenames, so I don't exactly ... Just to clarify on what we think as problem could differ: C:\Users\hzhou>ls *.txt new 2.txt
161.
by hzhou321 9y ago
> Which is not a problem. The command line was only one, historical UI. Not the be-all end-all of UIs, A similar trend is happening in electronic communication: from letter to email, to text, to emoji's. The text is just one histori
162.
by hzhou321 9y ago
> Meanwhile over in Windows land, all tools have been expected to deal with spaces in them for what is approaching 20 years. That is an excellent example that deserves a second look from a different aspect. ... it has trained a crop of c
163.
by hzhou321 9y ago
What about real world is that in real world, it is not context-free. There are real world situations -- such as selling a word processor to general public (especially) including clueless -- you need to deal with files with spaces, period. B
164.
by hzhou321 9y ago
Demanding the support of spaces in filenames significantly complicates code as simple space delimination no longer works and other delimination schemes are much more error prone -- forgetting balancing quotes, any one? While you are allowin
165.
by hzhou321 9y ago
It might be off topic but I just had this thought and like to write down… If you treat your program (and your problem) as math, then it is necessary to explicitly define all its boundaries. However many (most) problems in real life are not
166.
by hzhou321 9y ago
What did the author learned?
167.
by hzhou321 9y ago
It is not arguing for elliminating educations. It is arguing that we don't need force every one education. It is arguing that a forced education is not a really a good education.
168.
by hzhou321 9y ago
Good to learn! I always thought C-shell was aimed at scripting part (due to the sound of "C"); I guess I missed the boat.
169.
by hzhou321 9y ago
I agree that there is no value of saying "I don't know" in general. But sometime people would say "I don't know" as an emphasis on his "understanding" that there are something deeper than the current
170.
by hzhou321 9y ago
Crowd sentiment is very important (to many circumstances and understanding), so reading the 20-comment deep flame war is useful too. You just need make sure to read it from outside but not into it.
171.
by hzhou321 9y ago
There are risky risks, and there are affordable risks. One of the risky risks -- at main job, I am also very reluctant to commit to any new projects without emphasizing that I can not guarantee result but only effort up front first. Luckily
172.
by hzhou321 9y ago
I have always been wondering why don't we have shell program that don't do scripts -- no flow control and fancy macros, and separate program that run scripts -- no readline or job control (while pipes and redirects are simply trea
173.
by hzhou321 9y ago
Make sense. Then, it is because of the complexity we want to use the makefile. The include files is a mess for c/c++ because it poses no restrictions and people do abuse it. In my practice, I never put header files in the makefile. Th
174.
by hzhou321 9y ago
Very nice. It appears to be high time to create my own simple make.
175.
by hzhou321 9y ago
It can be more than that.
176.
by hzhou321 9y ago
I didn't find any, so I rolled my own 10 years ago. Most of its features are suited toward very limited users. E.g. it doesn't really support macro evaluation from arbitrary language, only from Perl currently (but general for any
177.
by hzhou321 9y ago
With a macro, you get guarantee of compile time evaluation, as well as compile time independent literal syntax double check. And you can do better than hint. You can double check the results explicitly. Since it's compile time evaluati
178.
by hzhou321 9y ago
If you use a general meta layer preprocessor such as MyDef, you may be able to construct macros that comes from evaluations of code in any languages (instead of restricted in eg. C++ with rather complicated compiler mechanics) A constexpr i
179.
by hzhou321 9y ago
I am so glad that I can live without these tips. As I grow older, every year I feel the need to cut down on my essentials. My .vimrc gets shorter every year. Earlier, I was so annoyed by the default parentheses highlighting yet so dislike t
180.
by hzhou321 9y ago
I suspect we (human) are very bad at hearing, computers already are doing are much better jobs than us. However, I suspect for most our communication, we do not actually hear the conversation -- we guess the conversation. Only when evidence

More ›