There is _no logic_ behind this behavior (unless one care to read all our discussions concerning this topic, and learn that there are several zeros in Pike, etc).
There is logic, but in a different way, as is covered by said discussion. You can win me over by good and solid arguments in a constructive discussion; I always try very hard to back up my opinions that way.
That's why I dislike what is going on. Not the language by itself. May be I was too hard in my wording, but I am just tired after several years trying to do _anything_.
What have you contributed besides a couple of bug reports/fixes and making suggestions for core language changes?
It's not surprising that it's hard to succeed with core changes; I know since I've tried that many times and failed more often than not. The core properties of a language are often the result of carefully weighing together a lot of different considerations. They interact with each other very deeply so changing one thing will affect other things, and most likely to the worse. Not to mention the practical problem with that there already is a whole lot of code out there that depends on things working in certain ways.
Suggest something better and we'll listen. For example, figure out a way to add real lightweight threads.
Nothing changed - Pike team is _always_ right.
I resent this, but nevertheless I recognize that it's an all too common opinion so there must be something that we, as the Pike team, is doing very wrong. I don't know exactly what it is though. Should we really accept suggestions that on the whole will make the language worse just to make you feel better? Do you after all this discussion still think that your idea got turned down just because it came from you?
because there is no good regexp module,
There hasn't been any objection to adding PCRE in at least the last one and a half years. Even though working glue already exists it's still not there yet. Why? Afaics it's because noone in the old core gang has taken it upon himself to do the actual work. Will you?
/ Martin Stjernholm, Roxen IS
Previous text:
2003-09-19 01:39: Subject: Re: float type weirdness
On Fri, Sep 19, 2003 at 01:15:01AM +0200, Per Hedbor () @ Pike (-) developers forum wrote:
Consider "float q = 123456789;" or "float q=1234567898765432123456789;"
Compiler must issue warning in such cases. It must _warn_, but not _enforce_, or _at least_ it must give the developer a choice.
And if you do not want to use pike, feel free not to.
This is different. I want, because it is nice, but there are some _inconsistences_, obvious but denied by the team.
Concering float, again:
2 == 2.0;
(1) Result: 0
2 < 4.0;
(2) Result: 1
2.0 < 4;
(3) Result: 1
There is _no logic_ behind this behavior (unless one care to read all our discussions concerning this topic, and learn that there are several zeros in Pike, etc).
That's why I dislike what is going on. Not the language by itself. May be I was too hard in my wording, but I am just tired after several years trying to do _anything_. Nothing changed - Pike team is _always_ right. At least my bug reports were accepted, that's good reason to stay alive, still... :)
It would be much better if Pike would give _a freedom_ to developers. But there is no freedom. There are rules, which are non-negotiable by definition.
Because legacy of Roxen in Pike modules is more important than something new, because there is no good regexp module, because Nettle is far better than openssl, because... you know what...
Sorry, but I am filled up with all this. I'll do what I do, what I intended to do, in Pike or whatever, but I lost my motivation to share anything that I might do... It wouldn't be accepted anyway, so who cares?
Regards, /Al
/ Brevbäraren