Member pointers do exist in C++. D Function delegates are different: They contain both a pointer to an object and a pointer to a function.
In order to call a function, with C++ member pointers you still need an object (used as the this pointer). With D member delegates, the this pointer is included in the delegate.
Borland C++ provides a proprietary extension called __closure with is pretty much the same.
What I found interesting was that they claim applications with garbage collection to be faster. I would never have expected this.
The D approach is pretty much taking the best from C++, Java and C#, and you can find a lot the stuff you were asking yourself "why is this not possible in [insert current language]" in it. For example what they call function deletates is really missing in C++.
However, some time will pass until a usable compiler will be available for *any* plattform.
The win32 reference states that the
"WH_GETMESSAGE hook enables an application to monitor messages about to be returned by the GetMessage or PeekMessage function. You can use the WH_GETMESSAGE hook to monitor mouse and keyboard input and other messages posted to the message queue."
Read the reference... SendMessage does not place messages into the thread's message queue. They are not being posted. They are also not being picked up by GetMessage or PeekMessage; instead, the window procedure is called directly.
The person who found out, MavEtJu, asked on some irc channel if anybody had a problem installing openssh, too. And just because a random mood of the universe, the (only?) person who answered was you because you had a checksum error, too, when you installed it.
Now, as it turnes out, the ip number this program contacts during build time happens to be your machine.
Do you have any explantation for this coincidence? It just sounds so unlikely. I mean, you might have been the first person who installed the trojan which phoned home to some other ip and then the package might have been modified again so it contacts your host... but how comes you have been on the same irc channel, #sage-au, at that moment?!?!
This is not meant to flame or suspect you, I'm just curious.
This might also have to do with the fact that most floppy drives are never used - and thus dirty as hell. Whenever I use a somewhat important floppy disk, I put in an old one before and let it gather the dirt. You can also compare the surface of it before and after this... might be interesting; if it gets scratches, you want to reconsider the idea of putting in the "important" disk.
Have you read the hidden comment about slashdot in the article?
A "daily news ticker" pointing to external resources is relatively easy to do, especially if you have software that finds much of the stuff (and readers that send in the rest)
I wonder when we will have CDROM/DVD/anything dirves which have "spinning" laser beams instead of the mechanical super fast stuff which is the weakest part in these drives. The disk would be in a fixed position. *That* should work at faster speeds.
it would be really useful if people would post reviews. Some short ones have been posted, but "rocks as hell"... well.
Any power users out there? Are there problems with fonts as told in the review of the beta? Can you create Access databases? Do macros/VBA programs work? Does the menu editor work? Do images in tables print well from word? Spell check? Help? Does the mouse feel right? Clipboard? Can you embed excel tables? Do ODBC connections from Access databases work?...
You miss the point: Telling "the user" to save the file in a certain way is not the way open source software will spread. Instread, it should open as many formats as possible.
A user should have the experience of "oh this program just opens my files without complaints and they still look right" and not "if I want to use this program with files people send me, I must tell them to save them in this or that way and they will not remember this and each time I have to get back to them and ask to send them again and they are set up and it is all quite messy".
This also concerns Word and Excel etc. KWord will be measured by the way it opens MSWord documents. Users expect all the pictures to be at the right place, the bullets appear at least similar and the tables' cell background be the same color and so on. And they are right, those users!
I agree, with one exception: The "C++ Builder Direct" Window which pops up every few weeks after it has made a connection to get the "latest news" from Borland. In Borland C++ Builder 4, you could only disable it by editing the registry. They have learned even here, though - there is a settings page for this in BCB 5.
I agree. The idea of picking up this topic is brilliant, but the article is biased in favour of OSS and it is clear that the author wishes that Microsoft's plans fail. Many of his arguments are determined by this wish:
OSS development process are far better at solving individual component issues than they are at solving integrative scenarios such as end-to-end ease of use.
Three years later, there is perhaps some truth to that.
Perhaps some truth? These days, Microsoft might add one paragraph to their new internal Haloween paper like this:
One of the major weaknesses of parts of the OSS community is the inability to admit their weaknesses.
Contest (Re:autoexec.bat and config.sys)
on
MS DOS: A Eulogy
·
· Score: 0
Don't look it up, be honest!
Correct arguments to share.exe to allocate enough memory to keep track of 100 files with one lock each? Win a free mode con argument syntax reference!
Also, whereever OS/2 is still in use, there will be 16 bit windows; and whereever 16 bit windows is, will be DOS. And there is still a lot of OS/2 - at least I can say this for the German financial world. They still use MS Access 2.0 (the 16 bit version) because of that, too.
I do not think it is gone just because there is no new OS containing it.
What about making settings to older non-PnP ISA cards? 3COM network adapters? And so on...
Re:ipsec, freeS/WAN and RedHat
on
Red Hat 7.2 Released
·
· Score: 2, Interesting
So I looked at cipe of which I was unaware so far. It seems to be a light weight tool to easily set up secure ip tunneling. This might already help us indeed, and we will take a closer look. It seems to implement a proprietary protocol and does not confirm to any standard except for its own. It may be sufficient to set up a secure ip tunnel between two Linux (or Unix) computers.
On the other hand, ipsec is a well defined standard defined in several RFC documents. FreeS/Wan is an implementation of it which also allows to communicatie with other systems implementing ipsec (routers).
FreeS/WAN is developed by non-US redidents only and they don't accept even single line patches from US citisens... So at least they think that there still are legal problems - dunno. Anyway, cipe seems to be the small solution where ipsec is the right one (and FreeS/WAN then tries to implement the right one; I don't know with how much success).
AFAIK it would be great if you'd schedule a reconsideration of it for some upcoming release of RedHat Linux.
I understand RedHat cannot integrate ipsec / FreeS/WAN into the Linux distribution because of US export restrictions.
Is there an "official" way to upgrade RH 7.2 to a kernel version with ipsec support (i.e. frees/wan) for European folks? The absence of this feature in RH becomes a more and more serious concern for my company.
Of course we know how to patch and compile a kernel. Maintenance must still be easy, though. Installing a custom kernel on several customer servers also means that we cannot use Redhat's update kernel RPMs but must maintain our own ones, so kernel (and possibly other packages) updates get complicated. It will not possible to respond on security issues as quickly as when using RH kernel RPMs.
It would be a great benefit for European customers if RedHat could at least draw the "official" procedure how to make this RH Linux version ipsec capable and then maintain this procedure as new kernel RPM packages or RedHat Linux versions appear.
Slashdot Mirror
Because women don't volunteer their time for FOSS development, men are sexist?
He didn't say that.
Being called a "homosexual" is "abuse"?
Yes, if the caller uses the term in an abusive context.
The device most likely does not exist.
The picture clearly shows a LED display with a certain depth behind the transparent cover, but the cuff is far too slim for that.
That's wrong, they work well in 32 Bit slots, too. See http://www.3ware.com/products/pdf/Motherboard_comp atibility_list.pdf
We have very good experiences with 3ware SATA cards, too. (In a 32 Bit slot.)
Member pointers do exist in C++. D Function delegates are different: They contain both a pointer to an object and a pointer to a function.
In order to call a function, with C++ member pointers you still need an object (used as the this pointer). With D member delegates, the this pointer is included in the delegate.
Borland C++ provides a proprietary extension called __closure with is pretty much the same.
The article is wrong. D is not at all C compatible. See Programming in D for C Programmers
The D approach is pretty much taking the best from C++, Java and C#, and you can find a lot the stuff you were asking yourself "why is this not possible in [insert current language]" in it. For example what they call function deletates is really missing in C++.
However, some time will pass until a usable compiler will be available for *any* plattform.
The win32 reference states that the "WH_GETMESSAGE hook enables an application to monitor messages about to be returned by the GetMessage or PeekMessage function. You can use the WH_GETMESSAGE hook to monitor mouse and keyboard input and other messages posted to the message queue."
Read the reference... SendMessage does not place messages into the thread's message queue. They are not being posted. They are also not being picked up by GetMessage or PeekMessage; instead, the window procedure is called directly.
Do we understand this correctly -
The person who found out, MavEtJu, asked on some irc channel if anybody had a problem installing openssh, too. And just because a random mood of the universe, the (only?) person who answered was you because you had a checksum error, too, when you installed it.
Now, as it turnes out, the ip number this program contacts during build time happens to be your machine.
Do you have any explantation for this coincidence? It just sounds so unlikely. I mean, you might have been the first person who installed the trojan which phoned home to some other ip and then the package might have been modified again so it contacts your host... but how comes you have been on the same irc channel, #sage-au, at that moment?!?!
This is not meant to flame or suspect you, I'm just curious.
This might also have to do with the fact that most floppy drives are never used - and thus dirty as hell. Whenever I use a somewhat important floppy disk, I put in an old one before and let it gather the dirt. You can also compare the surface of it before and after this... might be interesting; if it gets scratches, you want to reconsider the idea of putting in the "important" disk.
Have you read the hidden comment about slashdot in the article?
It might produce some good laughs reviewing the code. That's worth it.
I wonder when we will have CDROM/DVD/anything dirves which have "spinning" laser beams instead of the mechanical super fast stuff which is the weakest part in these drives. The disk would be in a fixed position. *That* should work at faster speeds.
As read on the heise article (German), blasphemia is prohibited in Italy - although the authorities rarely care.
Making corrections, - Radikal is not a "webzine" - it's a left radical magazine which once used to be published regulary.
heck, wow - i'm just overwhelmed by the obviously enormous number of married nerds here... anyone else NOT married? (sorry for being even more ot)
Folks,
it would be really useful if people would post reviews. Some short ones have been posted, but "rocks as hell"... well.
Any power users out there? Are there problems with fonts as told in the review of the beta? Can you create Access databases? Do macros/VBA programs work? Does the menu editor work? Do images in tables print well from word? Spell check? Help? Does the mouse feel right? Clipboard? Can you embed excel tables? Do ODBC connections from Access databases work? ...
Thanks!
> Any German readers who can enlighten us?
What you write is quite exactly the truth. Of course we have a big media industry. We don't have Holywood, though; I guess that's the difference.
Is that just from a random single program or is it a well-founded experience based result?
A user should have the experience of "oh this program just opens my files without complaints and they still look right" and not "if I want to use this program with files people send me, I must tell them to save them in this or that way and they will not remember this and each time I have to get back to them and ask to send them again and they are set up and it is all quite messy".
This also concerns Word and Excel etc. KWord will be measured by the way it opens MSWord documents. Users expect all the pictures to be at the right place, the bullets appear at least similar and the tables' cell background be the same color and so on. And they are right, those users!
I agree, with one exception: The "C++ Builder Direct" Window which pops up every few weeks after it has made a connection to get the "latest news" from Borland. In Borland C++ Builder 4, you could only disable it by editing the registry. They have learned even here, though - there is a settings page for this in BCB 5.
- OSS development process are far better at solving individual component issues than they are at solving integrative scenarios such as end-to-end ease of use.
Three years later, there is perhaps some truth to that.Perhaps some truth? These days, Microsoft might add one paragraph to their new internal Haloween paper like this:
Correct arguments to share.exe to allocate enough memory to keep track of 100 files with one lock each? Win a free mode con argument syntax reference!
I do not think it is gone just because there is no new OS containing it.
What about making settings to older non-PnP ISA cards? 3COM network adapters? And so on...
On the other hand, ipsec is a well defined standard defined in several RFC documents. FreeS/Wan is an implementation of it which also allows to communicatie with other systems implementing ipsec (routers).
FreeS/WAN is developed by non-US redidents only and they don't accept even single line patches from US citisens... So at least they think that there still are legal problems - dunno. Anyway, cipe seems to be the small solution where ipsec is the right one (and FreeS/WAN then tries to implement the right one; I don't know with how much success).
AFAIK it would be great if you'd schedule a reconsideration of it for some upcoming release of RedHat Linux.
Thanks!
I understand RedHat cannot integrate ipsec / FreeS/WAN into the Linux distribution because of US export restrictions.
Is there an "official" way to upgrade RH 7.2 to a kernel version with ipsec support (i.e. frees/wan) for European folks? The absence of this feature in RH becomes a more and more serious concern for my company.
Of course we know how to patch and compile a kernel. Maintenance must still be easy, though. Installing a custom kernel on several customer servers also means that we cannot use Redhat's update kernel RPMs but must maintain our own ones, so kernel (and possibly other packages) updates get complicated. It will not possible to respond on security issues as quickly as when using RH kernel RPMs.
It would be a great benefit for European customers if RedHat could at least draw the "official" procedure how to make this RH Linux version ipsec capable and then maintain this procedure as new kernel RPM packages or RedHat Linux versions appear.