cl-json-devel

cl-json-devel@common-lisp.net

116 discussions

Start a nNew thread

[cl-json-devel] cl-json 0.4, the patches
by Boris Smilga 13 Apr '09

13 Apr '09

Trying to send the patch bundle again. Please check the attachment. - B. Sm.

1 0

Re: [cl-json-devel] cl-json patch
by Henrik Hjelte 26 Feb '09

26 Feb '09

On Wed, Feb 25, 2009 at 2:58 PM, Ian Eslick wrote: > Hi Henrik, > > Would you mind putting this into the cl-json repository? It works around a > problem in ANSI interpretation that crops up in OpenMCL/ClozureCL but not in > the other lisps. > Sure, I have applied it now. /Henrik > diff -rN old-cl-json/src/encoder.lisp new-cl-json/src/encoder.lisp > 33c33 > < (type-error (e) > --- >> ((or type-error #+ccl simple-error) (e) > 38a39 >> (length s) ;; ISE: trips error in ccl which will fail silently above > > > >

2 1

[cl-json-devel] Is Israel a Democracy? -- The problem with intellectually insecure whites -- Should Christians Support Israeli Terrorism in Gaza?
by Lawrence Auster 23 Jan '09

23 Jan '09

The Jewish State of Israel has no constitution, nor does it name its borders. Israel's hidden constitution is Judaism. Israel's undeclared borders range from the Nile to the Euphrates rivers. Israel's desired jurisdiction extends over the entire Earth. It could not be more clear that the Jewish State follows a foreign policy which obeys Jewish Law as iterated in the Hebrew Bible, the Talmud, Maimonedes, the Cabalah, and the many commentaries and refinements of same. The Jews are genociding the native inhabitants of Palestine, just as their religion advises, and because their religion teaches them to do so. They treat non-Jews as if non-humans, just as their religion requires them to do. They make perpetual war on every nation on Earth, just as their genocidal Jewish God has instructed. The Jews of Israel are simply being Jews. Jews are an existential threat to the human race. Israel contains one third of the Jews of the World. It is not some aberration of the Jewish spirit, but the condensation and concentration of the perverse Jewish mentality, which malady also pervades the remaining two thirds of Jewry, who almost unanimously support the Jewish State, and who certainly do unanimously support the Jewish People and its consistent and constant crimes against the human race. Israel is Jewry and the danger of Israel is the danger of the Jewish People to all others, as the Jews have demonstrated each and every day of their existence. The Jews, the entire Jewish People of 15 million, will not relent until they have wiped out all non-Jews in "Greater Israel". They will not stop destroying all other cultures, nations, religions, ethnicities, races, competition, etc. until they are either stopped, or succeed in their ancient quest to destroy the human race. What Israel is doing is not some reaction to outside forces, nor was the formation of Israel a response to the Holocaust. Israel is simply following the plan laid out in the Jews' religious texts. The Jews have openly planned to take Palestine and genocide the native population of Palestine for some 2,500 years before the Holocaust. The Jews have openly complained that "anti-Semitism" is a threat that gives them the right to genocide the Palestinians, not merely since the advent of Nazism, but for some 2,500 years. The Jewish religion is the Constitution of the Jewish State of Israel, and, to a greater or lesser extent, the constitution of the nature of every Jew alive. The borders of Israel are the range the Jew roams over the entire World. The perverse Jewish mentality is inbred by a Jew's exposure to his parents and to his community. Judaism passes in the spit and slobber of Jewish mother telling her Jewish child that he is a "Jew", as much as Judaism passes in the poison and pain of a Talmudic tractate. The secular Jews did not suddenly come to life after the Enlightenment and the Jewish Reformation a body of vampires that appeared ex nihilo, in vacuo, mostly atheistical and undetached from formally practiced Judaism. Judaism is the Jew. It is a mindset that transcends and supercedes religion. It is a belief set, a way of life, a perception of one's self and one's relation to the World that makes a Jew, a Jew, and a danger to all of humanity. In fact, the religious shell of Judaism is like the stretched and infected skin of a lycanthropic pustule. When you lance it to cure the infection, the virus only becomes more contagious and spills directly on the non-Jew. The secular Jew is a deliberate product of the hyper-religious Jew, a monster created out of the hewed corpses of the fanatically religious Jew, a Golem which is conjured up to enter the World of the non-Jew and poison its blood, and boil its brain with a rabid lunacy that bites and spreads, until the infected community feeds on itself and fills the fields with rotting bloating bodies, where once human beings tilled the soil and tended to their families. The religious Jew created the secular Jew as an army of Esthers who seduce with open thighs, broad smiles, and a Siren call that lures in the non-Jew to cast his skull upon the jagged rocks and color the seas with his blood, sickened and blinded by the venereal disease of Judaism in secular form. Israel is not a secular democracy. It is a religious mockery. It is a rabid bat flying to the ends of the Earth, to end the Earth. No one will be free nor safe until the disease is quarantined and dies out. Source: http://www.ziopedia.org/articles/israel/how_can_israel_claim_to_be_a_%27dem… -------------------- The problem with intellectually insecure whites By Kevin MacDonald January 19, 2009 America will soon have a white minority. This is a much desired state of affairs for the hostile elites who hold political power and shape public opinion. But it certainly creates some management issues � at least in the long run. After all, it�s difficult to come up with an historical example of a nation with a solid ethnic majority (90% white in 1950) that has voluntarily decided to cede political and cultural power. Such transformations are typically accomplished by military invasions, great battles, and untold suffering. And it�s not as if everyone is doing it. Only Western nations view their own demographic and cultural eclipse as a moral imperative. Indeed, as I have noted previously, it is striking that racial nationalism has triumphed in Israel at the same time that the Jewish intellectual and political movements and the organized Jewish community have been the most active and effective force for a non-white America. Indeed, a poll in 2008 found that Avigdor Lieberman was the second most popular politician in Israel. Lieberman has advocated expulsion of Arabs from Israel and has declared himself a follower of Vladimir Jabotinsky, the leading pioneer of racial Zionism. The most popular politician in the poll was Benjamin Netanyahu � another admirer of Jabotinsky. Prime Minister Ehud Olmert and Foreign Minister Tzipi Livni are also Jabotinskyists. The racial Zionists are now carrying out yet another orgy of mass murder after a starvation-inducing blockade and the usual triggering assault designed to provoke Palestinian retaliation � which then becomes the cover for claims that Israel is merely defending itself against terrorism. This monstrosity was approved by overwhelming majorities of both Houses of Congress. The craven Bush administration did its part by abstaining from a UN resolution designed by the US Secretary of State as a result of a personal appeal by the Israeli Prime Minister. This is yet another accomplishment of the Israel Lobby, but one they would rather not have discussed in public. People might get the impression that the Lobby really does dictate US foreign policy in the Mideast. Obviously, such thoughts are only entertained by anti-Semites. But I digress. In managing the eclipse of white America, one strategy of the mainstream media is to simply ignore the issue. Christopher Donovan (�For the media, the less whites think about their coming minority status, the better�) has noted that the media, and in particular, the New York Times, are quite uninterested in doing stories that discuss what white people think about this state of affairs. It�s not surprising that the New York Times � the Jewish-owned flagship of anti-white, pro-multicultural media � ignores the issue. The issue is also missing from so-called conservative media even though one would think that conservatives would find the eclipse of white America to be an important issue. Certainly, their audiences would find it interesting. Now we have an article �The End of White America� written by Hua Hsu, an Assistant Professor of English at Vassar College. The article is a rather depressing display of what passes for intellectual discourse on the most important question confronting white people in America. Hsu begins by quoting a passage in F. Scott Fitzgerald�s The Great Gatsby in which a character, Tom Buchanan, states: �Have you read The Rise of the Colored Empires by this man Goddard?� � Well, it�s a fine book, and everybody ought to read it. The idea is if we don�t look out the white race will be�will be utterly submerged. It�s all scientific stuff; it�s been proved.� Buchanan�s comment is a thinly veiled reference to Lothrop Stoddard�s The Rising Tide of Color which Hsu describes as �rationalized hatred� presented in a scholarly, gentlemanly, and scientific tone. (This wording that will certainly help him when he comes up for tenure.) As Hsu notes, Stoddard had a doctorate from Harvard and was a member of many academic associations. His book was published by a major publisher. It was therefore �precisely the kind of book that a 1920s man of Buchanan�s profile � wealthy, Ivy League�educated, at once pretentious and intellectually insecure � might have been expected to bring up in casual conversation.� Let�s ponder that a bit. The simple reality is that in the year 2009 an Ivy League-educated person, "at once pretentious and intellectually insecure," would just as glibly assert the same sort of nonsense as Hsu. To wit: The coming white minority does not mean that the racial hierarchy of American culture will suddenly become inverted, as in 1995�s White Man�s Burden, an awful thought experiment of a film, starring John Travolta, that envisions an upside-down world in which whites are subjugated to their high-class black oppressors. There will be dislocations and resentments along the way, but the demographic shifts of the next 40 years are likely to reduce the power of racial hierarchies over everyone�s lives, producing a culture that�s more likely than any before to treat its inhabitants as individuals, rather than members of a caste or identity group. The fact is that no one can say for certain what multicultural America without a white majority will be like. There is no scientific or historical basis for claims like �the demographic shifts of the next 40 years are likely to reduce the power of racial hierarchies over everyone�s lives, producing a culture that�s more likely than any before to treat its inhabitants as individuals, rather than members of a caste or identity group.� Indeed, there is no evidence at all that we are proceeding to a color blind future. The election results continue to show that white people are coalescing in the Republican Party, while the Democrats are increasingly the party of a non-white soon-to-be majority. Is it so hard to believe that when this coalition achieves a majority that it will further compromise the interests of whites far beyond contemporary concerns such as immigration policy and affirmative action? Hsu anticipates a colorblind world, but affirmative action means that blacks and other minorities are certainly not treated as individuals. And it means that whites � especially white males � are losing out on opportunities they would have had without these policies and without the massive non-white immigration of the last few decades. Given the intractability of changing intelligence and other traits required for success in the contemporary economy, it is unlikely that 40 more years of affirmative action will attain the outcomes desired by the minority lobbies. Indeed, in Obama's America, blacks are rioting in Oakland over perceived racial injustices, and from 2002 �2007, black juvenile homicide victims increased 31%, while black juvenile homicide perpetrators increased 43%. Hence, the reasonable outlook is for a continuing need for affirmative action and for racial activism in these groups, even after whites become a minority. Whites will also lose out because of large-scale importation of relatively talented immigrants from East Asia. Indeed, as I noted over a decade ago, "The United States is well on the road to being dominated by an Asian technocratic elite and a Jewish business, professional, and media elite." Hsu shows that there already is considerable anxiety among whites about the future. An advertizing executive says, �I think white people feel like they�re under siege right now � like it�s not okay to be white right now, especially if you�re a white male. ... People are stressed out about it. �We used to be in control! We�re losing control�� Another says, "There�s a lot of fear and a lot of resentment." It's hard to see why these feelings won't increase in the future. A huge problem for white people is lack of intellectual and cultural confidence. Hsu quotes Christian (Stuff White People Like) Lander saying, "I get it: as a straight white male, I�m the worst thing on Earth." A professor comments that for his students "to be white is to be culturally broke. The classic thing white students say when you ask them to talk about who they are is, �I don�t have a culture.� They might be privileged, they might be loaded socioeconomically, but they feel bankrupt when it comes to culture � They feel disadvantaged, and they feel marginalized." This lack of cultural confidence is no accident. For nearly 100 years whites have been subjected to a culture of critique emanating from the most prestigious academic and media institutions. And, as Hsu points out, the most vibrant and influential aspect of American popular culture is hip-hop�a product of the African American urban culture. The only significant group of white people with any cultural confidence centers itself around country music, NASCAR, and the small town values of traditional white America. For this group of whites � and only this group � there is "a racial pride that dares not speak its name, and that defines itself through cultural cues instead�a suspicion of intellectual elites and city dwellers, a preference for folksiness and plainness of speech (whether real or feigned), and the association of a working-class white minority with 'the real America.'� This is what I term implicit whiteness � implicit because explicit assertions of white identity have been banned by the anti-white elites that dominate our politics and culture. It is a culture that, as Hsu notes, "cannot speak its name." But that implies that the submerged white identity of the white working class and the lack of cultural confidence exhibited by the rest of white America are imposed from outside. Although there may well be characteristics of whites that facilitate this process, this suppression of white identity and interests is certainly not the natural outcome of modernization or any other force internal to whites as a people. In my opinion, it is the result of the successful erection of a culture of critique in the West dominated by Jewish intellectual and political movements. The result is that educated, intellectually insecure white people these days are far more likely to believe in the utopian future described by Hsu than in hard and cautious thinking about what the future might have in store for them. It's worth dwelling a bit on the intellectual insecurity of the whites who mindlessly utter the mantras of multiculturalism that they have soaked up from the school system and from the media. Most people do not have much confidence in their intellectual ability and look to elite opinion to shape their beliefs. As I noted elsewhere, A critical component of the success of the culture of critique is that it achieved control of the most prestigious and influential institutions of the West, and it became a consensus among the elites, Jewish and non-Jewish alike. Once this happened, it is not surprising that this culture became widely accepted among people of very different levels of education and among people of different social classes. Most people are quite insecure about their intellectual ability. But they know that the professors at Harvard, and the editorial page of the New York Times and the Washington Post, and even conservative commentators like Rush Limbaugh and Sean Hannity are all on page when it comes to racial and ethnic issues. This is a formidable array, to the point that you almost have to be a crank to dissent from this consensus. I think one of the greatest triumphs of the left has been to get people to believe that people who assert white identity and interests or who make unflattering portrayals of organized Jewish movements are morally degenerate, stupid, and perhaps psychiatrically disturbed. Obviously, all of these adjectives designate low status. The reality is that the multicultural emperor has no clothes and, because of its support for racial Zionism and the racialism of ethnic minorities in America, it is massively hypocritical to boot. The New York Times, the academic left, and the faux conservatives that dominate elite discourse on race and ethnicity are intellectually bankrupt and can only remain in power by ruthlessly suppressing or ignoring the scientific findings. This is particularly a problem for college-educated whites. Like Fitzgerald's Tom Buchanan, such people have a strong need to feel that their ideas are respectable and part of the mainstream. But the respectable mainstream gives them absolutely nothing with which to validate themselves except perhaps the idea that the world will be a better place when people like them no longer have power. Hsu quotes the pathetic Christian Lander: "�Like, I�m aware of all the horrible crimes that my demographic has done in the world. ... And there�s a bunch of white people who are desperate � desperate � to say, �You know what? My skin�s white, but I�m not one of the white people who�s destroying the world.�� As a zombie leftist during the 1960s and 1970s, I know what that feeling of desperation is like � what it's like to be a self-hating white. We must get to the point where college-educated whites proudly and confidently say they are white and that they do not want to become a minority in America. This reminds me of the recent docudrama Milk, which depicts the life of gay activist Harvey Milk. Milk is sure be nominated for an Oscar as Best Picture because it lovingly illustrates a triumph of the cultural left. But is has an important message that should resonate with the millions of whites who have been deprived of their confidence and their culture: Be explicit. Just as Harvey Milk advocated being openly gay even in the face of dire consequences, whites need to tell their family and their friends that they have an identity as a white person and believe that whites have legitimate interests as white people. They must accept the consequences when they are harassed, fired from their jobs, or put in prison for such beliefs. They must run for political office as openly pro-white. Milk shows that homosexuals were fired from their jobs and arrested for congregating in public. Now it's the Southern Poverty Law Center and the rest of the leftist intellectual and political establishment that harasses and attempts to get people fired. But it's the same situation with the roles reversed. No revolution was ever accomplished without some martyrs. The revolution that restores the legitimacy of white identity and the legitimacy of white interests will be no exception. But it is a revolution that is absolutely necessary. The white majority is foolish indeed to entrust its future to a utopian hope that racial and ethnic identifications will disappear and that they won�t continue to influence public policy in ways that compromise the interests of whites. It does not take an overactive imagination to see that coalitions of minority groups could compromise the interests of formerly dominant whites. We already see numerous examples in which coalitions of minority groups attempt to influence public policy, including immigration policy, against the interests of the whites. Placing ourselves in a position of vulnerability would be extremely risky, given the deep sense of historical grievance fostered by many ethnic activists and organized ethnic lobbies. This is especially the case with Jews. Jewish organisations have been unanimous in condemning Western societies, Western traditions, and Christianity, for past crimes against Jews. Similar sentiments are typical of a great many African Americans and Latinos, and especially among the ethnic activists from these groups. The �God damn America� sermon by President Obama's pastor comes to mind as a recent notorious example. The precedent of the early decades of the Soviet Union should give pause to anyone who believes that surrendering ethnic hegemony does not carry risks. The Bolshevik revolution had a pronounced ethnic angle: To a very great extent, Jews and other non-Russians ruled over the Russian people, with disastrous consequences for the Russians and other ethnic groups that were not able to become part of the power structure. Jews formed a hostile elite within this power structure � as they will in the future white-minority America; Jews were �Stalin�s willing executioners.� Two passages from my review of Yuri Slezkine's The Jewish Century seem particularly appropriate here. The first passage reminds me of the many American Jews who adopt a veneer of support for leftist versions of social justice and racial tolerance while nevertheless managing to support racial Zionism and the mass murder, torture, and incarceration of the Palestinian people in one of the largest prison systems the world has ever seen. Such people may be very different when they become a hostile elite in a white-minority America. Many of the commentators on Jewish Bolsheviks noted the �transformation� of Jews [after the Bolshevik Revolution]. In the words of [a] Jewish commentator, G. A. Landau, �cruelty, sadism, and violence had seemed alien to a nation so far removed from physical activity.� And another Jewish commentator, Ia. A. Bromberg, noted that: the formerly oppressed lover of liberty had turned into a tyrant of �unheard-of-despotic arbitrariness��. The convinced and unconditional opponent of the death penalty not just for political crimes but for the most heinous offenses, who could not, as it were, watch a chicken being killed, has been transformed outwardly into a leather-clad person with a revolver and, in fact, lost all human likeness. ... After the Revolution, ... there was active suppression of any remnants of the older order and their descendants. ... The mass murder of peasants and nationalists was combined with the systematic exclusion of the previously existing non-Jewish middle class. The wife of a Leningrad University professor noted, �in all the institutions, only workers and Israelites are admitted; the life of the intelligentsia is very hard� (p. 243). Even at the end of the 1930s, prior to the Russification that accompanied World War II, �the Russian Federation�was still doing penance for its imperial past while also serving as an example of an ethnicity-free society� (p. 276). While all other nationalities, including Jews, were allowed and encouraged to keep their ethnic identities, the revolution remained an anti-majoritarian movement. The difference from the Soviet Union may well be that in white-minority America it will not be workers and Israelites who are favored, but non-whites and Israelites. Whites may dream that they are entering the post-racial utopia imagined by their erstwhile intellectual superiors. But it is quite possible that they are entering into a racial dystopia of unimaginable cruelty in which whites will be systematically excluded in favor of the new elites recruited from the soon-to-be majority. It's happened before. Kevin MacDonald is a professor of psychology at California State University�Long Beach. Permanent URL with hyperlinks: http://www.theoccidentalobserver.net/articles/MacDonald-Hsu.html ----------- Should Christians Support Israeli Terrorism in Gaza? A timely discussion between Rev. Ted Pike and Dr. David Duke, one especially important for the Christians in our audience http://www.davidduke.com/mp3/dukeradio090122DukeandPikeonGaza.mp3 In this vital discussion, Rev. Pike and Dr. Duke explore the Pro-Israel attitude of some Christian evangelical organizations, and why their position not only goes directly against Christian morality and decency, but actually is directly opposite of that expressed by Christian Scriptures. Today, Many Christians are instructed that Jews and today�s Israel has a special covenant� with God. In fact, the New Testament in the clearest of language states that the Jews �continued not in my covenant, and I considered them not, saith the Lord.� Here�s the quote that Christians aren�t supposed to notice.: 8:10 Not according to the covenant that I made with their fathers, in the day when I took them by the hand out of the land of Egypt; because they continued not in my covenant, and I regarded them not, saith the Lord. (Hebrews 8:10) They also don�t seem to notice that a 2000 year old Judaic war against Christianity that has been waged since time of Jesus Christ and still goes on today with the most powerful Jewish organizations attempting to destroy European and American traditions, that has even become a war on our Christmas traditions. Dr. Duke and Ted Pike also speak about how over a hundred thousand Christian Palestinians have suffered with their families from anti-Christian Israel! Christian support of Israel has resulted in the very birthplace of Jesus Christ, go from 90 percent Palestinian Christians to 35 percent today because of Israeli terror and occupation. They ask, �How could any Christian in good conscience support the anti-Christian state of Israel, bombing the homes, killing and maiming, torturing and oppressing fellow Christian men, women and children?� This is a vital show for every Christian reader and listener of DavidDuke.com. Next time, you hear someone say, �God tells us that we must support Israel� you will have the clear Christian answer that just the opposite is true! For documentation on this be sure to read some of the well-footnoted, sample chapters of Jewish Supremacism and My Awakening. Source : http://www.davidduke.com/general/should-christians-support-israeli-terroris… ------------------------------------- You or someone using your email adress is currently subscribed to the Lawrence Auster Newletter. If you wish to unsubscribe from our mailing list, please let us know by calling to 1 212 865 1284 Thanks, Lawrence Auster, 238 W 101 St Apt. 3B New York, NY 10025 Contact: lawrence.auster(a)att.net -------------------------------------

1 0

[cl-json-devel] Latest Parenscript breaks cl-json
by Leslie P. Polzer 08 Dec '08

08 Dec '08

SYMBOL-TO-JS has been renamed to SYMBOL-TO-JS-STRING (patch attached). Also, the current cl-json web page leads users to the obsolete darcs repo of Parenscript. Guys have switched to git. Thanks, Leslie -- LinkedIn Profile: http://www.linkedin.com/in/polzer Xing Profile: https://www.xing.com/profile/LeslieP_Polzer Blog: http://blog.viridian-project.de/

3 5

[cl-json-devel] deployment of customized decoder and streaming encoder
by Boris Smilga 23 Nov '08

23 Nov '08

Hello Henrik and everyone. I have got a message from a user recently who expressed his interest in CL-JSON, so I felt obliged to somewhat press the issue of shipping out a new version which would integrate the customizable decoder and a streaming encoder. Now I see that decoder-args.lisp and decoder- vars.lisp have been commited to the central repository, but the question which one to choose and whether any further enhancements are necessary stays open. Well, I can only repeat that my own prefence is for decoder-vars.lisp, and, if no-one would like to further discuss this issue, I'll allow myself to start bringing the code from that file over into decoder.lisp. Patches to be posted to this list as usual. Sincerely, - B. Smilga.

2 1

[cl-json-devel] [PATCH] Explicitly test for alist instead of type error
by Stephen Compall 29 Aug '08

29 Aug '08

Clozure CL (current SVN, maybe release I dunno) does this: (map 'list #'identity '(x . "abc")) => (x #\b #\c) Which breaks the alist case in encoder.lisp. So, pending a fix for Clozure, I made a workaround that tests explicitly for a proper alist instead. Attached is the Darcs patch: -- I write stuff at http://failex.blogspot.com/ now. But the post formatter and themes are terrible for sharing code, the primary content, so it might go away sooner or later.

1 1

[cl-json-devel] usage of cl-json
by srinivasa reddy kadem 26 Aug '08

26 Aug '08

Already we are using cl-json in our product development, I'm not sure which version we are using now. But it is belongs to old source code(I think it is downloaded very long back). Our team did some customization in the source code which meet our requirements. I want to update this into newer versions. Please let me know how to use it and where I can download latest version of cl-json.In what way it should be embedded it into our application. Let me know you need any further clarification. Anybody please help me or give suggestions. -- Thanks, Reddy

2 2

[cl-json-devel] proposed: improvements to decoder customization
by Boris Smilga 24 Aug '08

24 Aug '08

[This memo started as a follow-up to the e-mail exchange between Henrik and your humble author (now recorded in the TODO file), but, on reviewing it, I thought that it would perhaps be of some interest to the broader readership of cl-json-devel. This is to explain the rather personal style of discourse, and make apologies to a reader who might —but who need not!— feel excluded.] §1. The design of the improved decoder interface laid out below came to be as I was considering an application of CL-JSON that would involve local structured storage of transmitted data in a Berkeley DB. In such a setting one would like to bypass creating Lisp data structures from JSON input, instead packing it directly to FFI C data to be processed by libdb. The question that I asked myself was how to (re)design the decoder so that this task could be dealt with gracefully. I have also checked the scheme against the several probable sets of requirements you had described in your e-mail: > Configurable: I really would want to have it optional exactly how > to decode and encode objects. You are probably right in that your > solution is a good default behaviour, but it will not be perfect in > every situation for every user. So if possible, I would like to > have the decoding and encoding configurable. So backwards > compatibility does not really mean backwards, it means > compatibility between different setups. For example, when doing > testcases or a simple json-bind the old alist setup is good, for a > more advanced setup your code is great. For a secure setup you will > probably want to have access control to what objects you are > allowed to create and so on. One solution will never be sufficient > for everyone. §2. Hence, the general principles which should be obeyed by the implementation, are: A. Separation of concerns. The implementation should comprise a fixed basic level to handle the parsing, JSON well-formedness, and flow control; and a customizable level to produce Lisp data (or perform some other JSON-driven task, as it might please the user to enjoin). You were very rightfully incensed against my intermingling parsing with looking for prototype in READ-JSON-OBJECT. It will become clear below how this can be done away with. B. Fine grain. Not only the handling of objects, but also that of other JSON types should be customizable. In particular, the handling of arrays and strings should be customizable on elemental level, i.e. the user should have a way to determine how the decoder handles elements of arrays and strings. In handling objects, customization should be available for keys as well as for key-value pairs. §3. This suggests a design similar in spirit to SAX, with a set of handlers triggered by “events”. The current implementation partly follows this scheme by providing the *JSON-OBJECT-FACTORY... callbacks, but there are more kinds of events than can be handled by those three; here's a tentatively exhaustive list: 1. An atomic constant (integer, real, or boolean). 2a. Beginning of string. 2e. A string character or escape sequence. 2z. End of string. 3a. Beginning of array. 3e. An array element. 3z. End of array. 4a. Beginning of object. 4k. An object property key. 4v. An object property value. 4z. End of object. Accordingly, we need at least as many handlers. The handlers for (1), (2e), (3e), (4k/v) shall be passed the token that triggered the event; (2a), (3a), and (4a) shall produce some fresh “accumulator” value that is then piped through successive calls to (2e), (3e), and (4k/v), respectively. E.g., reading the JSON {"f\u0151o": [1, true]} could result in the following flow of calls to handlers (I use mnemonic names of function-valued handler variables, which are certainly not definitive): READ-JSON-OBJECT 4a: *BEGINNING-OF-OBJECT-HANDLER* () produces some value (⇒) O READ-JSON-STRING 2a: *BEGINNING-OF-STRING-HANDLER* () ⇒ S 2e: *STRING-CHAR-HANDLER* (#x66, S) ⇒ S′ 2e: *STRING-CHAR-HANDLER* (#x151, S′) ⇒ S″ 2e: *STRING-CHAR-HANDLER* (#x6f, S″) ⇒ S‴ 2z: *END-OF-STRING-HANDLER* (S‴) ⇒ T 4k: *OBJECT-KEY-HANDLER* (T) ⇒ K READ-JSON-ARRAY 3a: *BEGINNING-OF-ARRAY-HANDLER* () ⇒ A 1: *INTEGER-HANDLER* ("1") ⇒ I 3e: *ARRAY-ELEMENT-HANDLER* (I, A) ⇒ A′ 1: *BOOLEAN-HANDLER* ("true") ⇒ B 3e: *ARRAY-ELEMENT-HANDLER* (B, A′) ⇒ A″ 3z: *END-OF-ARRAY-HANDLER* (A″) ⇒ V 4v: *OBJECT-VALUE-HANDLER* (K, V, O) ⇒ O′ 4z: *END-OF-OBJECT-HANDLER* (O′) ⇒ P, which is also the return value of READ-JSON-OBJECT. The nature of the values O, S, S′, S″, S‴, T, etc. is of absolutely no concern to the base level of the decoder whose only duty is to faithfully pass them around. For one, a dumb JSON syntax checker can have all handlers set to (CONSTANTLY T). §4. Now the current list semantics can be expressed straightforwardly in terms of these handlers: *BEGINNING-OF-ARRAY-HANDLER* ⇒ (lambda () (let ((list (cons nil nil))) ; First element is never used (cons list list))) ; First and last pair of the list *ARRAY-ELEMENT-HANDLER* ⇒ (lambda (elt accumulator) (destructuring-bind (head . last) accumulator (cons head (setf (cdr last) (cons elt nil))))) *END-OF-ARRAY-HANDLER* ⇒ (lambda (accumulator) (coerce (cdar accumulator) *json-array-type*)) *BEGINNING-OF-OBJECT-HANDLER* ⇒ same as *BEGINNING-OF-ARRAY-HANDLER* *OBJECT-KEY-HANDLER* ⇒ #'json-intern *OBJECT-VALUE-HANDLER* ⇒ (lambda (key value accumulator) (destructuring-bind (head . last) accumulator (cons head (setf (cdr last) (cons (cons key value) nil))))) *END-OF-OBJECT-HANDLER* ⇒ #'cdar *INTEGER-HANDLER* ⇒ #'parse-integer You can easily reconstruct the rest. §5. Our CLOS semantics is a more tricky affair. If I may allow myself to reiterate what I previously said about the handling of prototype fields: > READ-JSON-OBJECT works by reading in the key string and the colon > separator, and then recursively calling READ-JSON to consume > characters from the input and construct the object which would be > the corresponding value. With my modifications, when the key > "prototype" (or whatever the name shoud be) is encountered on the > input, the decoder is told that the value we are going to construct > shall be the prototype object. If we were not able to communicate > this beforehand, we'd have to do much post-processing of the > factory object: look up the prototype (note that, at this point, we > would not know the package and could not yet intern the keys, so > that the matching would be done on strings, degrading the > performance), convert it to some internal format (note that we > would not be able to predict accurately enough what it would have > been decoded to, as that may be influenced by user-side > configuration), remove the prototype and key from the factory, and > only then could we create the object. Put rather abstractly, to overcome this difficulty we need a means to pass certain information from outer to inner recursive calls of READ-JSON-OBJECT, and between handlers invoked on the same level. I currently see two options of implementing this: A. “Accumulator” return values of (3a/e) and (4a/k/v) handlers (what is signified by A, A′, ..., and O, O′ in the above example) are passed down as additional arguments to the recursive calls to READ-JSON-OBJECT and READ-JSON-ARRAY, and are then also passed to (3a) and (4a) handlers in these inner functions (and perhaps also to (1) and (2a)). The (4k) handler, like (4v), receives and produces an “accumulator” value rather than a representation of the key. Thus, the flow in the above example becomes: ... 4k: *OBJECT-KEY-HANDLER* (T, O) ⇒ O′ READ-JSON-ARRAY (..., O′) 3a: *BEGINNING-OF-ARRAY-HANDLER* (O′) ⇒ A ... 3z: *END-OF-ARRAY-HANDLER* (A″) ⇒ V 4v: *OBJECT-VALUE-HANDLER* (V, O′) ⇒ O″ ... This would allow for an implementation of the CLOS semantics along the following lines: *BEGINNING-OF-OBJECT-HANDLER* ⇒ (lambda (&optional (above-accumulator nil not-toplevel)) (let* ((prototype (if not-toplevel (caar above-accumulator))) (list (cons prototype nil))) (cons list list))) *OBJECT-KEY-HANDLER* ⇒ (lambda (key accumulator) (destructuring-bind (head . last) accumulator (let ((prototype (car head))) (if (and (not prototype) (string= key (symbol-name *prototype-name*))) (cons (cons t (cdr head)) last) (cons head (setf (cdr last) (cons (cons key nil) nil))))))) *OBJECT-VALUE-HANDLER* ⇒ (lambda (value accumulator) (destructuring-bind (head . last) accumulator (if (typep value 'prototype) (cons (cons value (cdr head)) last) (progn (setf (cdar last) value) accumulator)))) *END-OF-OBJECT-HANDLER* ⇒ (lambda (accumulator) (destructuring-bind ((prototype . fields) . last) accumulator (let ((*json-object-prototype* prototype)) (json-factory-make-object fields)))) B. In addition to custom handlers, the user is given the possibility to provide a list of dynamic variables which he wishes to have “JSON-structure scope”. That is, the bodies of READ-JSON-OBJECT and READ-JSON-ARRAY are wrapped in PROGVs which establish new dynamic bindings for these variables (using their outer-level bindings for respective initial values). If a handler sets a structure-scope variable, the new value is then visible to all subsequent handlers until the current READ-JSON-OBJECT or READ-JSON-ARRAY loop exits. By constrast, the handlers on the outer levels never see the value change. The flow in the example is unaltered, and the CLOS semantics is implemented thus: *JSON-STRUCTURE-SCOPE-VARIABLES* ⇒ '(*json-object-prototype*) *BEGINNING-OF-OBJECT-HANDLER* ⇒ (lambda () (let ((list (cons nil nil))) (cons list list))) *OBJECT-KEY-HANDLER* ⇒ (lambda (key) (if (and (not *json-object-prototype*) (string= key (symbol-name *prototype-name*))) (setq *json-object-prototype* t)) key) *OBJECT-VALUE-HANDLER* ⇒ (lambda (key value accumulator) (destructuring-bind (head . last) accumulator (if (typep value 'prototype) (progn (setq *json-object-prototype* value) accumulator) (cons head (setf (cdr last) (cons (cons key value) nil)))))) *END-OF-OBJECT-HANDLER* ⇒ (lambda (accumulator) (json-factory-make-object (cdar accumulator))) The choice between the options A and B seems to be one between simplicity of interface and efficiency: a lot of nested PROGVs are likely to incur some cost overhead (I do not feel myself qualified enough to predict exactly how much). On the other hand, handlers are rather more readable, as you can see in the above comparison, and the interface also stays more intuitive that way. §6. Returning to my BDB + CL-JSON application: the (2a), (3a), (4a) handlers coud be customized to call data constructor / initializer functions over the FFI, and (2z), (3z), (4z) to call the DB put method. The uppermost call to READ-JSON would be wrapped up as a transaction. That would be it. Sincerely, - B. Smilga.

3 7

[cl-json-devel] proposed: improvements to decoder customization
by Boris Smilga 24 Aug '08

24 Aug '08

On 7 Aug 2008, at 03:51, Boris Smilga wrote: > On 4 Aug 2008, at 00:14, Henrik Hjelte wrote: >> 2. I think the A (Accumulator) version seems to be good, and If it >> has >> other advantages as you write, I think we should go for it. > > Actually, I rather prefer B, which is cleaner, though, probably, worse > performing. I think I'm going to implement both and run some heavy > workload tests to see how bad the regression could be, and then we'll > decide. Please find attached a patch bundle with the implementation of the decoder in two flavours: with extra arguments and with dynamic json-structure-scope variables. They are in two separate files, with much code overlap between the two. So let us choose which one we eventually want. The workload tests were done as follows. First, I generated a random huge json file (see the code in the attached file random-json.lisp; the output was generated by running (with-open-file (s #p"test.in" :direction :output) (generate-random-json s 120)) which yielded some 214 KB of json data, with maximum depth of nesting 21). The contents of the file was then fed to DECODE-JSON under different setups, by running (with-open-file (s #p"test.in") (time (decode-json s))) NB: To get comparable results for CLOS semantics, I had to reboot Lisp between tests. This is because implementations usually employ optimizations geared toward stable CLOS-style classes. With the kind of transient classes that we create from prototypeless JSON objects the optimizations actually can cause performance to degrade, sometimes severely. See my exchange with Gary Byers from Clozure on the openmcl-devel mailing list: http://clozure.com/pipermail/openmcl-devel/2008-August/008458.html, http://clozure.com/pipermail/openmcl-devel/2008-August/008463.html. Hence, now that we have a customizable decoder, I would either scrape transient classes altogether, substituting some default prototype (e.g. {"lispClass":"cons"}, or some wrapper around alists, as in st-json), or else post big notices in red letters: “Thou Shalt Not Omit Prototypes” all over the place. The test results are thus: Clozure CL v. 1.2 RC1 (DarwinPPC32) on 1.5 GHz PowerBook G4 with 1.25 GB RAM. List semantics: With the extra-args approach: 1.442 sec. run time, 10,209,120 bytes allocated. With the dynamic-vars approach: 1.571 sec. run time, 12,317,928 bytes allocated. CLOS semantics: Extra-args: 10.870 sec. run time, 34,559,256 bytes allocated. Dynamic-vars: 10.961 sec. run time, 34,972,216 bytes allocated. ************ SBCL 1.0.18 on the same. List semantics: Extra-args: 1.163 sec. run time, 18,111,072 bytes allocated. Dynamic-vars: 1.218 sec. run time, 18,407,344 bytes allocated. CLOS semantics: Extra-args: 7.193 sec. run time, 96,173,152 bytes allocated. Dynamic-vars: 7.451 sec. run time, 96,767,968 bytes allocated. ************ CLisp 2.40 on the same: List semantics: Extra-args: 1.351 sec. run time, 8,328,464 bytes allocated. Dynamic-vars: 1.406 sec. run time, 8,447,900 bytes allocated. CLOS semantics: Extra-args: 9.057 sec. run time, 28,362,544 bytes allocated. Dynamic-vars: 9.112 sec. run time, 28,775,504 bytes allocated. ************ SBCL 1.0.17 on 2 GHz AMD 64 3000+ with 512 MB RAM. List semantics: Extra-args: 0.472 sec. run time, 19,891,336 bytes allocated. Dynamic-vars: 0.471 sec. run time, 20,187,112 bytes allocated. CLOS semantics: Extra-args: 2.171 sec. run time, 80,166,760 bytes allocated. Dynamic-vars: 2.180 sec. run time, 80,724,960 bytes allocated. I would say that the regression is fairly benign, never more than 9% run time and 20% memory, on average 2% run time and 4% memory. I allow myself once again to state my preference for the dynamic-vars approach, which has a much cleaner interface. Cleaner—especially so as the elaborate passing-around of handler states could be done away with altogether and replaced by handler-side changing of the state of dynamic variables. The implementation of the two simple semantics in decoder-vars.lisp illustrates this point: a beginning-of-structure handler initializes the variables *ACCUMULATOR* and *ACCUMULATOR-LAST*, and structure-element handlers imperatively modify their state. As the variables have json-structure scope, sub-structures cannot clobber their parent structures' accumulators. There were two more important sets of changes. Firstly, the basic json reader was redesigned to work in terms of tokens. A token is either a number literal, a symbol, or a punctuation mark (string characters and escape sequences can be seen as tokens as well). This modularizes the design into a lower-level tokenizer part and a higher-level decoder part. Secondly, I have substituted my own version of CAMEL-CASE-TO-LISP to handle conventions like "JSONAllCapitals" (⇒ "+JSON+-ALL-CAPITALS"), "TWO_WORDS" (⇒ "+TWO-WORDS+"), and "camelCase_mixed_4_PARTS" (⇒ "CAMEL-CASE--MIXED--+4-PARTS+"). Sincerely, - B. Smilga.

2 1

[cl-json-devel] proposed patch: encoding and unencoding CLOS objects
by boris.smilga＠gmail.com 23 Jul '08

23 Jul '08

*** Rationale *** §1. A significant problem I perceive with CL-JSON in its present state is that the operations ENCODE-JSON and DECODE-JSON are not reasonably inverse. E.g.: (ENCODE-JSON-TO-STRING (DECODE-JSON-FROM-STRING "{\"foo\":null,\"bar \":null}")) => "[[\"foo\"],[\"bar\"]]" and (ENCODE-JSON-TO-STRING (DECODE-JSON-FROM-STRING "{}")) => "null" §2. This is the most painful kind of example, because the JSON object having even a single non-null field results in a proper value. Thus, the type of a JSON object emitted by an application that uses ENCODE-JSON can depend not only on the type of the source Lisp object but on its internal structure as well. This is not to say that ENCODE-JSON fusing Lisp vectors with lists and symbols and characters with strings, or DECODE-JSON fusing false with null are particularly pleasant; still, in theses cases we are able to predict typing across JSON interface. Note, however, that (ENCODE-JSON-TO-STRING (DECODE-JSON-FROM-STRING "[]")) would also yield "null". This has to be dealt with as well. §3. The root of the problem is the design decision of representing JSON objects as Lisp alists, and the solution I propose is to revert that decision and represent JSON objects as CLOS objects. This is quite feasible if we make use of meta-object protocol capabilities implemented in a more or less standardized way across most contemporary Common Lisps. In the simple form, decoding a well-formed JSON object should result in the creation of an anonymous class (i.e. an instance of STANDARD-CLASS) with such slots as found in the JSON object. Next, we create an instance of the anonymous class and populate its slots. Conversely, encoding a CLOS object Z should be done by iterating over the value of (CLASS-SLOTS (CLASS-OF Z)) and emitting a name:value pair for each slot bound in Z. §4. Attached herewith is a series of patches implementing the idea. However, I have ventured a step further by allowing JSON objects to include metadata which specify that CLOS objects are to belong (or else inherit) to non-anonymous CLOS classes. The metadata are passed as the field of the object whose name is ``prototype''. (More accurately, the name is determined by the symbol which is the value of the special variable *PROTOTYPE-NAME*: the value (FUNCALL *SYMBOL-TO-STRING-FN* *PROTOTYPE-NAME*) must be STRING= to the name of the field. I have judged the default value 'PROTOTYPE more or less developer-friendly, as the field ``prototype'' in JavaScript objects is already reserved for special purposes and so is unlikely to conflict with anyone's user-level naming schemes. Below, I invariably call this field the prototype field.) The value of the prototype field should be an object, called the prototype, in which the following fields are meaningful: "lispClass":C, "lispSuperclasses":[C1,...,Cn] and "lispPackage":P (all other fields are ignored). The following rules are employed when decoding a JSON object X to a CLOS object Z: (D1) If the prototype of X has a "lispClass":C field, Z shall be an instance of the class identified by the name C, and all fields of X which have no correspondence among the slots of the class C are discarded. (D2) If the prototype of X has a "lispSuperclasses":[C1,...,Cn] field, Z shall be an instance of an anonymous class C whose superclasses are identified by the names C1,...,Cn. The fields of X which have no correspondence among any of the slots of the classes C1,...,Cn are defined in C as direct slots. As a special case, if n=1 and all of X's fields (omitting the prototype) are defined as slots in C1 then Z shall be an instance of C1. (D3) If the prototype has both a "lispClass":C and a "lispSuperclasses":[C1,...,Cn] fields then the rule D1 applies and the latter field is ignored. (D4) If the prototype has a "lispPackage":P field, then the names of the classes in both other fields and the names of the fields in X are interned in the package specified by P instead of the default package KEYWORD. Of course, all names (including P itself) are converted from camel case before using them in Lisp. (D5) If the class of the resulting object Z provides for a slot whose name is the value of the special variable *PROTOTYPE-NAME* (JSON::PROTOTYPE by default) then that slot shall be bound to the object which internally represents the prototype of X (an instance of the class JSON::PROTOTYPE, qv. the code). NB: this slot is never created by the decoder on its own authority but always inherited from the class or superclasses specified. (D6) If the prototype has a "lispClass":"cons" field and such "lispPackage":P field that the interned class name is COMMON-LISP:CONS, the rule D1 does not apply. Instead, Z shall be an alist whose conses' cars are the names and whose conses' cdrs are the respective values of the fields in X. The field names are interned in P, and the prototype field itself is omitted. (D7) If the prototype has a "lispClass":"hashTable" field and such "lispPackage":P field that the interned class name is COMMON-LISP:HASH-TABLE, the rule D1 does not apply. Instead, Z shall be a hash table whose keys are the names and whose values are the respective values of the fields in X. The field names are interned in P, and the prototype field itself is omitted. (D8) The value of null for any of the three fields of a prototype is equivalent to the field being absent. X lacking or having a null prototype is equivalent to the prototype having all null fields. §5. Conversely, when a CLOS object Z is encoded, the encoded JSON object X shall include a prototype reconstructed from Z per following rules: (E1) If the class of Z has a name, the prototype shall have a "lispClass":C field, where C is that name (it is assumed here and below that all names are converted to camel case). (E2) If the class of Z does not have a name, the prototype shall have a "lispSuperclasses":[C1,...,Cn] field, where C1,...,Cn are the names of that class's superclasses. (E3) If Z is an alist, the prototype shall have a "lispClass":"cons" field. (E4) If Z is a hash table, the prototype shall have a "lispClass":"hashTable" field. (E5) The prototype shall have a "lispPackage":P field, where P is the name of a package such that any one of the names C or C1,...,Cn, and any one of the names of the slots bound in Z, is a symbol (either direct or inherited) in the package. (Mutatis mutandis if Z is an alist or a hash table.) If there is no such package, P shall be an unspecific package name, and the program shall signal a warning condition. §6. Below are some examples of the modified decoder / encoder. I have marked the printout with double bars, and the result with =>. This is from an SBCL session; I have also tested the examples in OpenMCL. (IN-PACKAGE JSON) => #<PACKAGE "JSON"> (DECODE-JSON-FROM-STRING "{\"foo\":null,\"bar\":null}") => #<#<STANDARD-CLASS NIL {1268AC79}> {1268D979}> (DESCRIBE *) || #<#<STANDARD-CLASS NIL {1268AC79}> {1268D979}> || is an instance of class #<STANDARD-CLASS NIL {1268AC79}>. || The following slots have :INSTANCE allocation: || BAR NIL || FOO NIL (DESCRIBE (CLASS-OF **)) || #<STANDARD-CLASS NIL {1268AC79}> is a class. It is an instance of || STANDARD-CLASS. || It has no name (the name is NIL). || The direct superclasses are: (STANDARD-OBJECT), and the direct subclasses || are: (). || The class is finalized; its class precedence list is: || (#<STANDARD-CLASS NIL {1268AC79}> STANDARD-OBJECT SB-PCL::SLOT- OBJECT T). || There are 0 methods specialized for this class. (ENCODE-JSON-TO-STRING ***) => "{\"bar\":null,\"foo\":null,\"prototype\":{\"lispClass\":null, \"lispSuperclasses\":[\"standardObject\"],\"lispPackage\":\"json\"}}" (DESCRIBE (DECODE-JSON-FROM-STRING "{}")) || #<STANDARD-OBJECT {11D01F71}> || is an instance of class #<STANDARD-CLASS STANDARD-OBJECT>. (DEFSTRUCT FOO BAR BAZ) => FOO (ENCODE-JSON-TO-STRING (MAKE-FOO :BAR 10 :BAZ 20)) => "{\"bar\":10,\"baz\":20,\"prototype\":{\"lispClass\":\"foo\", \"lispSuperclasses\":null,\"lispPackage\":\"json\"}}" (DECODE-JSON-FROM-STRING *) => #S(FOO :BAR 10 :BAZ 20) (DECODE-JSON-FROM-STRING "{\"bar\":10,\"baz\":20,\"quux\":50,\"prototype\":{\"lispClass\": \"foo\",\"lispPackage\":\"json\"}}") => #S(FOO :BAR 10 :BAZ 20) (DECODE-JSON-FROM-STRING "{\"bar\":10,\"baz\":20,\"quux\":50,\"prototype\":{\"lispClass\": \"cons\",\"lispPackage\":\"json\"}}") => ((BAR . 10) (BAZ . 20) (QUUX . 50)) (MAPHASH (LAMBDA (K V) (PRINT K) (PRINT V)) (DECODE-JSON-FROM-STRING "{\"bar\":10,\"baz\":20,\"quux\":50,\"prototype\":{\"lispClass\": \"hashTable\",\"lispPackage\":\"json\"}}")) || || BAR || 10 || BAZ || 20 || QUUX || 50 => NIL §7. The following additional names are exported from the package JSON: *PROTOTYPE-NAME* special variable (default: JSON::PROTOTYPE) A symbol which determines the name of the prototype field in a JSON object and the name of a slot in a CLOS object which may hold prototype information. As a special case, if *PROTOTYPE-NAME* is NIL the encoder does not add a prototype field when encoding an object that misses a prototype slot or key, and the decoder does not search for or treat in a special manner a prototype field in the input. The latter behaviour results in the ``simple semantics'' of §3: (LET ((*PROTOTYPE-NAME* NIL)) (DECODE-JSON-FROM-STRING "{\"bar\":10,\"baz\":20,\"prototype\":{\"lispClass\":\"foo\", \"lispPackage\":\"json\"}}")) => #<#<STANDARD-CLASS NIL {12524FA1}> {125290A9}> (DESCRIBE *) || #<#<STANDARD-CLASS NIL {12524FA1}> {125290A9}> || is an instance of class #<STANDARD-CLASS NIL {12524FA1}>. || The following slots have :INSTANCE allocation: || BAR 10 || BAZ 20 || PROTOTYPE #<#<STANDARD-CLASS NIL {12521579}> {12524219}> (DESCRIBE (SLOT-VALUE ** 'PROTOTYPE)) || #<#<STANDARD-CLASS NIL {12521579}> {12524219}> || is an instance of class #<STANDARD-CLASS NIL {12521579}>. || The following slots have :INSTANCE allocation: || LISP-CLASS "foo" || LISP-PACKAGE "json" *JSON-ARRAY-TYPE* special variable (default: VECTOR) A type specifier which determines what type to coerce JSON arrays to. The default value has been chosen to cope with the kind of problem mentioned in §2. Thus, unless *JSON-ARRAY-TYPE* is set to LIST the value of (DECODE-JSON-FROM-STRING "[]") shall be #(), yielding "[]" when re-encoded. WITH-OLD-DECODER-SEMANTICS macro Ensures backward compatibility with the old CL-JSON decoder. It can be called as (WITH-OLD-DECODER-SEMANTICS FORM*) where FORMs are an implicit PROGN. FORMs are executed in an environment where JSON objects are invariably decoded to alists, JSON arrays to lists, array keys interned in the package KEYWORD, and array fields called ``prototype'' (or whatever is specified by *PROTOTYPE-NAME*) receive no special treatment. E.g.: (WITH-OLD-DECODER-SEMANTICS (DECODE-JSON-FROM-STRING "{\"bar\":10,\"baz\":20,\"prototype\":{\"lispSuperclasses\": [\"foo\",\"bar\"],\"lispPackage\":\"json\"}}")) => ((:BAR . 10) (:BAZ . 20) (:PROTOTYPE (:LISP-SUPERCLASSES "foo" "bar") (:LISP-PACKAGE . "json"))) *** Summary of patches *** Sun Dec 23 18:10:00 MSK 2007 boris.smilga(a)gmail.com * Added CLOS / MOP infrastructure. Sun Dec 23 18:13:34 MSK 2007 boris.smilga(a)gmail.com * Added decoding of objects to CLOS objects, hash tables or alists. Sun Dec 23 18:16:10 MSK 2007 boris.smilga(a)gmail.com * Added decoding of arrays to vectors or lists. Sun Dec 23 18:17:05 MSK 2007 boris.smilga(a)gmail.com * Added WITH-OLD-DECODER-SEMANTICS. Sun Dec 23 18:17:44 MSK 2007 boris.smilga(a)gmail.com * Added encoding of CLOS objects, and prototypes for alists and hash tables.

3 3

← Newer
1
2
3
4
5
6
7
8
9
...
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

cl-json-devel