Location for backend code

Thread: Location for backend code

Search this list only Search all lists
Location for backend code
United States	2007-07-24 23:44:25
What should be the proper place to put backends in source control? boost/langbinding/xxx/... libs/langbinding/xxx/... ? Oh, and I just thought of something. We may want to name the Java backend something other than "Boost.Java", since "Java" is trademarked. Maybe "Boost.JNI" or something. Maybe I'm getting ahead of myself, though. -- John Moeller fishcorngmail.com ------------------------------------------------------------ ------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Boost-langbinding mailing list Boost-langbindinglists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost -langbinding

Re: Location for backend code
United States	2007-07-24 23:56:15
John Moeller wrote: > What should be the proper place to put backends in source control? > > boost/langbinding/xxx/... > libs/langbinding/xxx/... > > ? Theoretically, meaning not with the existing code, you should only need to place backend code in "libs/langbinding/src/backend/xxx/...". > Oh, and I just thought of something. We may want to name the Java > backend something other than "Boost.Java", since "Java" is trademarked. > Maybe "Boost.JNI" or something. Maybe I'm getting ahead of myself, > though. Yea, how rude to trademark the name of an island. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software .com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo ------------------------------------------------------------ ------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Boost-langbinding mailing list Boost-langbindinglists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost -langbinding

Re: Location for backend code
United States	2007-07-25 00:52:19
Rene Rivera wrote: > John Moeller wrote: >> What should be the proper place to put backends in source control? >> >> boost/langbinding/xxx/... >> libs/langbinding/xxx/... >> >> ? > > Theoretically, meaning not with the existing code, you should only need > to place backend code in "libs/langbinding/src/backend/xxx/...". Oh, so the whole thing, headers and all? That would be more convenient. >> Oh, and I just thought of something. We may want to name the Java >> backend something other than "Boost.Java", since "Java" is trademarked. >> Maybe "Boost.JNI" or something. Maybe I'm getting ahead of myself, >> though. > > Yea, how rude to trademark the name of an island. -- John Moeller fishcorngmail.com ------------------------------------------------------------ ------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Boost-langbinding mailing list Boost-langbindinglists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost -langbinding

[1-3]

about | contact Other archives ( Real Estate discussion Medical topics )