I've search around the ReactOS site, the mailing lists, and the Wiki, and haven't seen this subject out there much. We have an older application that runs on Windows over a network connection. The software must be run over the network and must have a mapped network drive to function correctly. I know that Samba-TNG is available for ReactOS, but this seems to only smbclient and no way to mount or map a network share. Are there any plans or current efforts to support mapped network drive functionality?
Thanks - Nick
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
Hi Guys,
So After a LONG hiatus I've finally decided to get back into writing
code for ReactOS. Some (most?) of you may not remember me. I've been
lurking on the lists since 2000-2001, and was an active developer with
CVS access for a while back in 2002-2003 (check the commit messages
for rcampbell, also submitted quite a few patches). have never stopped
reading (although i was/am using a different email address), but
haven't touched the code before now. I have a couple of questions:
1) Is my SVN username active? The username is rcampbell. If not,
I'll just use bugzilla. 2) Any documentation on coding guidelines
such as styles, etc. or rules? I'm sure this has changed since my
heyday.
Thanks,
Richard Campbell
> No, it's just a matter of coding style used in the kernel.
What is a logical basis for adopting this particular rule? Sometimes it is
not just a matter of preference.
These parentheses are unnecessary for humans, and if they are not needed for
compilers or some other tools, they are bad! Without them, the bug could be
noticed earlier.
Cheers,
Dmitry
> I personally feel consistent application of the style is also important,
> and that there does not exist a reason to deviate from the established
> coding style in this situation.
I agree that it is good to follow the consistent coding style. The question
is this style itself is good.
I meant the abstract case of ((a = b) && (c = d)), not the concrete case of
((ConvKey == HashEntry->ConvKey) && (Length == Ncb->NameLength)).