1. Trademarking
- Posted by Adam Weeden <theskaman at MINDSPRING.COM> Apr 12, 1999
- 365 views
------=_NextPart_000_0035_01BE848E.162FB3C0 charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Due to the proliferation of incudes (font comes to mind), constants, and = function/procedures that share the same name, I propose that we have a = trademarking system that way, we dont get conflicts (I know I'm sick of = them), this would also prevent backwards compatibility issues in the = future. In order to not let someone trademark standard constants (TRUE, = FALSE, etc.) we should have a RDS stamped constant.e that will have = all common constants. I dont know who could handle the trademarking = process (I would never volunteer anyone, including RDS, for such a large = task). Worse comes to worse I will implement this if everyone agrees to = abide by it. Thanks for the cooperation, Adam Weeden WeedenSoft Technologies ------=_NextPart_000_0035_01BE848E.162FB3C0 charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Diso-8859-1" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT size=3D2>Due to the proliferation of incudes (font comes to = mind),=20 constants, and function/procedures that share the same name, I propose = that we=20 have a trademarking system that way, we dont get conflicts (I know I'm = sick of=20 them), this would also prevent backwards compatibility issues in the=20 future. In order to not let someone trademark standard constants = (TRUE,=20 FALSE, etc.) we should have a RDS stamped constant.e that = will have=20 all common constants. I dont know who could handle the = trademarking=20 process (I would never volunteer anyone, including RDS, for such a large = task). Worse comes to worse I will implement this if everyone = agrees to=20 abide by it.</FONT></DIV> <DIV> </DIV> <DIV><FONT size=3D2>Thanks for the cooperation,</FONT></DIV> <DIV><FONT size=3D2>Adam Weeden</FONT></DIV> ------=_NextPart_000_0035_01BE848E.162FB3C0--
2. Re: Trademarking
- Posted by "Boehme, Gabriel" <gboehme at MUSICLAND.COM> Apr 12, 1999
- 328 views
Adam Weeden wrote: >Due to the proliferation of incudes (font comes to mind), constants, and >function/procedures that share the same name, I propose that we have a >trademarking system that way, we dont get conflicts (I know I'm sick of >them), this would also prevent backwards compatibility issues in the >future. In order to not let someone trademark standard constants (TRUE, >FALSE, etc.) we should have a RDS stamped constant.e that will have all >common constants. I dont know who could handle the trademarking process >(I would never volunteer anyone, including RDS, for such a large task). >Worse comes to worse I will implement this if everyone agrees to abide by >it. I thought RDS was working on a solution to the namespace/scope issue, to help prevent some of the problems mentioned here. Is that still true, Robert, or is the Linux port taking priority at this time? Just wondering, Gabriel Boehme ------- Men are ruled, at this minute by the clock, by liars who refuse them news, and by fools who cannot govern. G.K. Chesterton -------
3. Re: Trademarking
- Posted by Robert Craig <rds at ATTCANADA.NET> Apr 12, 1999
- 346 views
Gabriel Boehme writes: > I thought RDS was working on a solution to the > namespace/scope issue, to help prevent some of the > problems mentioned here. Is that still true, Robert, or is the > Linux port taking priority at this time? I consider the namespace issue to be a very high priority for the next major release. A "pre-alpha" Linux release will probably come first however. Regards, Rob Craig Rapid Deployment Software http://members.aol.com/FilesEu/