[AOLSERVER] [PATCH] * Minor lisp.c cleanup.
---
nsd/lisp.c | 31 ++-
1 files changed, 14 insertions(+), 17 deletions(-)
diff --git a/nsd/lisp.c b/nsd/lisp.c
index d67db74..b019763 100644
--- a/nsd/lisp.c
+++ b/nsd/lisp.c
@@ -58,16 +58,16 @@ static const char *RCSID = @(#) $Header:
/Users/dossy/Desktop/cvs/aolserver/nsd
Ns_List *
Ns_ListNconc(Ns_List *l1Ptr, Ns_List *l2Ptr)
{
-Ns_List *lPtr;
-
-if (l1Ptr != NULL) {
-for (lPtr = l1Ptr; ((lPtr-rest) != NULL); lPtr = lPtr-rest)
- ;
-lPtr-rest = l2Ptr;
-return (l1Ptr);
-} else {
-return (l2Ptr);
-}
+if (l1Ptr == NULL)
+ return l2Ptr;
+
+Ns_List *lPtr = l1Ptr;
+
+for (lPtr = l1Ptr; ((lPtr-rest) != NULL); lPtr = lPtr-rest)
+ ;
+
+lPtr-rest = l2Ptr;
+return (l1Ptr);
}
@@ -154,13 +154,10 @@ Ns_ListNreverse(Ns_List *lPtr)
Ns_List *
Ns_ListLast(Ns_List *lPtr)
{
-if (lPtr == NULL) {
-return NULL;
-} else {
-for (; lPtr-rest != NULL; lPtr = lPtr-rest)
- ;
-return lPtr;
-}
+if (lPtr != NULL)
+ while (lPtr-rest != NULL)
+ lPtr = lPtr-rest;
+return lPtr;
}
--
1.7.5.4
--
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
___
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk
Re: [AOLSERVER] Question re CPU usage
On 02/16/2014 05:33 PM, Thorpe Mayes wrote: Hi. What would cause the following: Normally the CPU percent is in the low single digits. Now it gets as high as 333%. I am looking at recent changes, but I am not sure what to look for. Do you have any custom .adp pages, URL handers, or other TCL scripts running within AOLserver? Or is this just a bone stock install without any requests? My hunch is that there is a particular page or script causing this. -ayan -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
[AOLSERVER] Is there anyone out there?
aolserver-talk has been quiet for a while. Has the discussion moved somewhere else? -ayan -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
[AOLSERVER] Roadmap Revisited (was Re: Is there anyone out there?)
On 05/11/2014 10:50 AM, Dossy Shiobara wrote: On 5/10/14 9:38 PM, Ayan George wrote: aolserver-talk has been quiet for a while. Has the discussion moved somewhere else? Not that I'm aware of ... but, it's possible there's some NaviServer-focused list that has much more activity than this one. First, sorry for the rambly email. I remember a really encouraging thread titled Roadmap - 4.6 and beyond but nothing seemed to come of it. Perhaps now that usage is fairly low it is time to start making bold changes to improve and modernize the code AND to attract new developers and users. I don't think inertia or alienating users would be a valid argument against changes at this point. This is a good time to set some hard goals, delegate tasks, etc. This time, however, maybe Dossy can suss out what seems worthwhile and make it happen? Personally, I would like to see the following: * Define the scope and goals of AOLserver. Personally, I'd like AOLserver to be a high performance, programmable, TCL based web server for Unix-like operating systems. * Identify subsystems and assign a maintainer to each. Initially this may be the same person or small group but the goal would be to delegate ownership. * Completely commit to a traditional git workflow. Accept patches on the -talk submitted using list for review. Have subsystem maintainers apply patches. Dossy then pulls from each maintainer's tree to cut a release. * Drop Windows support unless it is exceedingly easy to do. Right now there are 86 #ifdef _WIN32 instances in the code -- IMHO, there should be 0. Why worry about alienating an incredibly small (maybe non-existent) sliver of an already tiny community? * Allow, encourage, maybe insist upon more modern programming techniques. There is a lot of classic C89 or pre-C89 code in AOLserver. Many open source projects balk at using C99 features citing compiler support and developer familiarity but C99 is about 15 years old now and well supported. I think AOLserver would be a more attractive if we explicitly required C99 features that can improve the quality of the code (inline declarations, declarations in for() loops, restrict pointers, etc.). A simple goal like converting for() loops to c99 in-loop-declarations or adding restrict keywords where useful would give developers an opportunity to get familiar with the code without doing any heavy lifting. * Modernize the main event loop. Perhaps use libevent for socket multiplexing and thread dispatch. This will allow it to take advantage of superior multiplexing techniques like kqueue() and epoll(). * SPDY, HTTP 1.1, HTTP 2.0? * Support for deferred accepts (FreeBSD AcceptFilters, Linux TCP_DEFER_ACCEPT). * Ongoing code clean-up, feature addition, optimization, and bug fixes. Bottom line though is that I'm not sure if we should be afraid to break anything. I don't think anyone will notice. :^) -ayan -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
Re: [AOLSERVER] Roadmap Revisited (was Re: Is there anyone out there?)
On 05/11/2014 01:35 PM, Ayan George wrote: * Completely commit to a traditional git workflow. Accept patches on the -talk submitted using list for review. Have subsystem maintainers apply patches. Dossy then pulls from each maintainer's tree to cut a release. Eh -- this bullet point is mangled. I meant accept patches submitted to -talk using git format-patch. -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
Re: [AOLSERVER] Aolserver - Postgresql - not recognizing columns added to tables
Also, can you see the new columns by searching the information schema in both psql and aolserver? -- ___ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
Re: [AOLSERVER] Aolserver - Postgresql - not recognizing columns added to tables
On 08/09/2015 03:03 PM, Thorpe Mayes wrote: Hi, I have moved postgresql databases from one server to another. This was done by dumping the database, moving the resulting file to the new server, and then restoring the dumped file on the new server. When I directly select rows via postgresdql (on the new server) from a table that had a column added after the table was created and before the table was moved to the new server there are not any problems. However, when I try to do the same select from within a tcl script an error is thrown - the column does not exist. When I run the sql statement without the offending column, there is not a problem. So, it appears to me that the problem is with columns that have been added to tables via alter table… Can anyone shed some light on this problem? What version of PostgreSQL are you running and which version of libpq is your nspostgres linked against? When you moved servers, did you also change the version of postgres you're using? -ayan -- ___ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
