
What I said above doesn't remove my praise to mORMot, of course, but saying brook is a toy is far from fair.
#Free pascal convert timestamp to date free#
(well, I really wish mormot will fully support free Pascal in the near future!)

In additional to **simplicity** (which has/is always a good thing and nowadays people embrace ), another benefit of Brook is **cross-platform**. Want to use another ORM or data persistence library? No problem, and most importantly - it's easy and simple from the coder's POV, since usually you can just plug-in an extension or module. That being said, the philosophies beyind all those Sinatra-inspired frameworks like brook are:Ī quote from the wikipedia: the goal is to "quickly creating web-applications with minimal effort." Probably this helps with mORMot's switching to Linux ?įor instance, the opf is a joke and features are pretty with respect, I think what you said is not fair to the brook framework.Īlthough I have not fully evaluated and test it, IIRC, just like Python's popular and elegant Flask web framework ( ), I guess Brook fro FPC is also inspired by the Sinatra framework for Ruby ( ).Īctually, almost every mainstream languages has one or more Sinatra-inspired web framework that are quite widely used, well, except Dephi ( (s … by_Sinatra) Stand alone service/daemon (with embedded daemon server). On a side effect, it is noted that Brook can run in four modes:ĬGI (with any HTTP server like Apache, nginx etc.) Lazarus wizards for installation and usage - With Lazarus, development is easier with the Brook wizards, only a few clicks are required to start and configure your Brook projects.Ĭould you help to share your opinions on it ? e.g., architectural, performance-wise, roadmap/future. Brook is powerful even if you don't use REST – but you will want to use it. REST architecture support – REST is an architecture able to simplify and standardize data requests and replies. You will really appreciate Brooks' good JSON support. JSON native support – JSON is widespred in the web for data exchange purposes. Less instantiations, less coding, with an elegant syntax. Integrated data persistance – Brook offers a table object where data can be handled.
#Free pascal convert timestamp to date how to#
Brook knows how to receive a request and choose the correct URL and the correct method to reply to it. Īdvanced routes management – Actions are performed by means of routes. Please, let me know how I can help to fix this issue.It appears to be an interesting framework and just turns 3.0 (A lot of messages in fpc-pascal mail list today ). I would say this is a rather critical bug. Sym:=tsym(tprocdef(pd.genericdef).localst.findwithhash(hashedid)) It fails in the determine_generic_def function on line 401: I compiled a debug version of the FPC compiler so I can see the stack line numbers and units. Must be probably related to generics implementation (changes in FPC 3.x).

You have the exception Additional information: $ fpc SimpleObjectsTest.dpr -MObjFPC -gw2 -l -g -gl -gp -XMPASCALMAIN_ALIAS -dFPC_RTL Free Pascal Compiler version 3.0.4 for i386 Copyright (c) 1993-2017 by Florian Klaempfl and others Target OS: Win32 for i386 Compiling SimpleObjectsTest.dpr Compiling TestUnit.pas Fatal: Compilation aborted An unhandled exception occurred at $004575E9: EAccessViolation: Access violation $004575E9 line 370 of symbase.pas $004FBB62 line 401 of pdecl.pas $004FB016 line 626 of pdecl.pas $004FBBF3 line 876 of pdecl.pas $0050D967 line 2218 of psub.pas $00509EFF line 307 of psub.pas $0050CCE9 line 1808 of psub.pas $0050D158 line 1959 of psub.pas $0050DE78 line 2394 of psub.pas $0050DD01 line 2425 of psub.pas $00422D0C line 1756 of cclasses.pas $0050DF71 line 2434 of psub.pas $005544A0 line 1057 of pmodules.pas $005543AC line 981 of pmodules.pas $00438D5D line 368 of parser.pas $0054B4D4 line 1734 of fppu.pas $005532E6 line 484 of pmodules.pasĮrror: C:\lazarus\fpc\3.0.4\bin\i386-win32\ppc386.exe returned an error exitcode Steps to reproduce:įpc SimpleObjectsTest.dpr -MObjFPC -gw2 -l -g -gl -gp -XMPASCALMAIN_ALIAS -dFPC_RTLĮdit the TestUnit.pas so you only modify the timestamp (or you can add a comment.)Ĭompile again with the same command as in 2)
