ExpireyDate is the date when you left Pirey.
Also, this posting doesn't follow the theme of the postings before, but it's a valid point on the topic.
ExpireyDate is the date when you left Pirey.
Also, this posting doesn't follow the theme of the postings before, but it's a valid point on the topic.
Next time you should build the same thing but use Triple Parity.
Hard-coding to "C:/Program Files" has never been reasonable. The folder name has been localized in different language versions of Windows since Windows95 I think, so the application could never have worked on Spanish/German/French/Dutch/etc. computers.
This is fine as long as he adds:
#define 10 CountChar(dest, "%")/2
Also, did Substitute return whether it had done any replacement? If
not, the author had no choice but to call it multiple times and hope
things would be alright.
@Jaime said:
You guys write software; make a front end that collects the data and posts to their web server. It doesn't excuse Apple's behavior, but at least it minimizes the impact on you.
...and then sell that front end as an iPhone app!
Stormy/Rainy weather may hinder cell phone reception, so it would probably interfer with cloud usage from mobile devices.
@airdrik said:
You might grok the code base for usages of LOG_ALL to see if it is being (mis)used anywhere. Who knows but that you might learn something "useful" (if not for personal enlightenment, for the entertainment of your fellows in these parts).
@Severity One said:
So how would you do
setLogging( QLoggingLevel )
?You don't call setLogging(QLoggingLevel), you call setLogging(int), and you pass in the combination of logging levels or'd together. Of course that should only be done on app startup by the log configurator after reading in the logging configuration from file. Similarly the log level check should be wrapped within the corresponding log.error/log.warn/log.info/etc. method call to make things simple for the people who are using this framework (and to make it easy to switch to a more standard logging framework when they find out that that's all they're rewriting anyway).
setLogging(LOG_ERRORS | LOG_WARNINGS <font size="2">| </font>LOG_COMMENTS <font size="2">| </font>LOG_METHOD_ENTRY <font size="2">| </font>LOG_METHOD_EXIT<font size="2"> | </font>LOG_SERVER_CALLS);
But what if another log type is added later? Then you'd have to find every instance of setLogging(...) and add the new log type. Wouldn't it be cool to have aconstant like LOG_ALL, which is defined right there together with the other constants, so you won't forget to change it?
LOG_ALL could also be used to enumerate all logging types, by iterating over all bits of that constant.
Also, the constant may be useful during debugging. You've got the applications halted in a debugger and you need logging right now? Just enable LOG_ALL and don't worry about what types to enable.
@morbiuswilters said:
I'll make the problem go away permanently for $34 and two double cheeseburgers (vegetarian, of course).
May even be vegan; who knows
It should be fine if, by default, it's only enabled for trusted sites that probably send useful notifications only. Like e.g. Facebook.
Obviously, he should hav done it like this:
while (true) { switch (Console.KeyAvailable) {
case true:key = Console.ReadKey() // do logic here with the new key here</pre><pre> case false:</pre><pre> Thread.Sleep (100); }
}
So it won't wait for 100ms between keypresses!
"cla"+Tab is probably as fast as typing class. And "cl"+Tab becomes ambigous (you might have wanted to write "cloche").